Property talk:P108

Documentation

employer
person or organization for which the subject works or worked

Represents

Data type

Domain

According to this template: human (Q5)

According to statements in the property:
human (Q5), fictional character (Q95074), fictional human (Q15632617), fictional location (Q3895768), group of humans (Q16334295), human whose existence is disputed (Q21070568), mythical character (Q4271324) or humanoid robot (Q584529)

When possible, data should only be stored as statements

Allowed values

All kinds of employers: businesses, educational facilities, branches of government, non-profit organizations, provider of honorary positions etc. (note: this should be moved to the property statements)

Example

Albert Verlinde (Q1965433) → Stage Entertainment Germany (Q181192)
Neil Armstrong (Q1615) → National Aeronautics and Space Administration (Q23548)
Angela Merkel (Q567) → Zentralinstitut für Physikalische Chemie (Q26882567)
Hayley Westenra (Q231985) → UNICEF (Q740308)

Robot and gadget jobs

DeltaBot does the following jobs:

Move source to qualifier

Tracking: same

no label (Q42533327)

Tracking: usage

Category:Pages using Wikidata property P108 (Q23908983)

See also

affiliation string (P6424), affiliation (P1416), occupation (P106)

Lists

Items with no other statements

Most recently created items

Items with novalue claims

Items with unknown value claims

Usage history (total)

Usage history (main statement)

Map of people by place values:

January 1st dates

Database reports/Humans with missing claims/P108

Database reports/Constraint violations/P108

Map

Random list

Living people protection class

property that may violate privacy (Q44601380)

Proposal discussion

Current uses

Total	2,413,232
Main statement	2,389,680	99% of uses
Qualifier	23,486	1% of uses
Reference	66	<0.1% of uses

Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Value type “organization (Q43229), fictional organization (Q14623646), group of humans (Q16334295), human (Q5), fictional character (Q95074), government agency (Q327333), airport (Q1248784), periodical (Q1002697), parish (Q102496), legendary figure (Q13002315), fictional location (Q3895768), anthology (Q105420), fictional company (Q5446565), website (Q35127), company (Q783794), duo (Q10648343), fictional human (Q15632617), theatre company (Q11812394), structure of worship (Q1370598), government organization (Q2659904), television program (Q15416), palace (Q16560), podcast (Q24634210), association (Q15911314), television channel (Q2001305), cultural institution (Q3152824), administrative territorial entity (Q56061), newspaper (Q11032), radio program (Q1555508), military base (Q245016), mine (Q820477), educational institution (Q2385804), manufacturer (Q13235160), facility (Q13226383), campaign (Q6056746), radio channel (Q1474440), mythological Greek character (Q22988604), human whose existence is disputed (Q21070568), corporation (Q167037)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value organization (Q43229), fictional organization (Q14623646), group of humans (Q16334295), human (Q5), fictional character (Q95074), government agency (Q327333), airport (Q1248784), periodical (Q1002697), parish (Q102496), legendary figure (Q13002315), fictional location (Q3895768), anthology (Q105420), fictional company (Q5446565), website (Q35127), company (Q783794), duo (Q10648343), fictional human (Q15632617), theatre company (Q11812394), structure of worship (Q1370598), government organization (Q2659904), television program (Q15416), palace (Q16560), podcast (Q24634210), association (Q15911314), television channel (Q2001305), cultural institution (Q3152824), administrative territorial entity (Q56061), newspaper (Q11032), radio program (Q1555508), military base (Q245016), mine (Q820477), educational institution (Q2385804), manufacturer (Q13235160), facility (Q13226383), campaign (Q6056746), radio channel (Q1474440), mythological Greek character (Q22988604), human whose existence is disputed (Q21070568), corporation (Q167037) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Value type Q43229, Q14623646, Q16334295, Q5, Q95074, Q327333, Q1248784, Q1002697, Q102496, Q13002315, Q3895768, Q105420, Q5446565, Q35127, Q783794, Q10648343, Q15632617, Q11812394, Q1370598, Q2659904, Q15416, Q16560, Q24634210, Q15911314, Q2001305, Q3152824, Q56061, Q11032, Q1555508, Q245016, Q820477, Q2385804, Q13235160, Q13226383, Q6056746, Q1474440, Q22988604, Q21070568, Q167037, SPARQL

Qualifiers “start time (P580), end time (P582), end cause (P1534), point in time (P585), duration (P2047), valid in period (P1264), position held (P39), part of (P361), replaces (P1365), replaced by (P1366), appointed by (P748), applies to name of subject (P5168), object of statement has role (P3831), subject has role (P2868), identity of object in context (P4626), identity of subject in context (P4649), has characteristic (P1552), has cause (P828), field of work (P101), work location (P937), location (P276), has subsidiary (P355), subject named as (P1810), object named as (P1932), nature of statement (P5102), statement is subject of (P805), statement supported by (P3680), statement disputed by (P1310), sourcing circumstances (P1480), determination method or standard (P459), refine date (P4241), earliest date (P1319), latest start date (P8555), earliest end date (P8554), latest date (P1326), floruit (P1317), CNRS research group ID (P4550), affiliation string (P6424), archive URL (P1065), archive date (P2960), reason for deprecated rank (P2241), reason for preferred rank (P7452), applies to name of object (P8338), of (P642), affiliation (P1416), applies to work (P10663), occupation (P106)”: this property should be used only with the listed qualifiers. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#allowed qualifiers, SPARQL

Contemporaries:
if [item A] has this property (employer (P108)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Contemporary, SPARQL

Type “human (Q5), fictional character (Q95074), fictional human (Q15632617), fictional location (Q3895768), group of humans (Q16334295), human whose existence is disputed (Q21070568), mythical character (Q4271324), humanoid robot (Q584529)”: item must contain property “instance of (P31), subclass of (P279)” with classes “human (Q5), fictional character (Q95074), fictional human (Q15632617), fictional location (Q3895768), group of humans (Q16334295), human whose existence is disputed (Q21070568), mythical character (Q4271324), humanoid robot (Q584529)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Type Q5, Q95074, Q15632617, Q3895768, Q16334295, Q21070568, Q4271324, Q584529, SPARQL

Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Entity types

Conflicts with “instance of (P31): magazine (Q41298), newspaper (Q11032), periodical (Q1002697), website (Q35127)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P108#Conflicts with P31, SPARQL

This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

What is it?

Description reads "organization for which the subject works or worked". But that sounds very broad, for example, a person may be sub-contracted but not directly employed by the organisation they are working for.

Should use be limited to organisations which the person has worked for directly, or what?

One issue is that we may never be able to establish exactly which organisations a person was employed by. We don't have access to people's employment contracts.

Perhaps the property name should be changed to worked for which would be broader, and can be more easily sourced. Danrok (talk) 20:55, 25 February 2013 (UTC)[reply]

Sure why not. Go for it! I see someone reverted my change from "employer" to "employed by". It's too bad we can't explain changes in edit summaries; I had a reason! Espeso (talk) 18:18, 13 March 2013 (UTC)[reply]

Suproperty of P1416 (affiliation)

A more general type of relationship between people and organisations is given by affiliation (P1416). I have added a subproperty of (P1647) statement to record this. I think the constraints on affiliation (P1416) should be relaxed to account for this; see the discussion on P1416. --Markus Krötzsch (talk) 09:56, 22 July 2015 (UTC)[reply]

Person as the employer?

The description says the employer must be an organization. The property has Wikidata item of this property (P1629): employer (Q3053337), which can be a person or company. --AVRS (talk) 17:06, 27 April 2016 (UTC)[reply]

@AVRS: agent (Q24229398) means "a person or a company" d1g (talk) 18:09, 12 August 2017 (UTC)[reply]

@D1gggg: So? Are you suggesting that I add it, or? --AVRS (talk) 19:32, 15 August 2017 (UTC)[reply]

@AVRS: I also think that the employer can be a person, and I added human and fictional character as value type constraint. --Neo-Jay (talk) 21:51, 26 May 2018 (UTC)[reply]

problem with P39 it says political

How can I enter an ordinary contractor employee (Q703534) using P108? d1g (talk) 18:08, 12 August 2017 (UTC)[reply]

location (P276) as qualificator

Can location (P276) be used as Wikidata qualifier for employer (P108). Especially where there are many locations? Breg Pmt (talk) 10:58, 30 September 2017 (UTC)[reply]

I'll add work location (P937), it seems appropriate. Ghouston (talk) 07:55, 26 September 2018 (UTC)[reply]

changed constraint "as" to "subject has role"

I removed the constraint P794 (P794) and add subject has role (P2868). This is in line with the deprecation of P794. Noting that position held (P39) which had a similar function is already in place. — billinghurst sDrewth 06:58, 14 October 2017 (UTC)[reply]

Directorships?

Do we have a good way to represent that someone was a director (= board member) of a company? They are often not employees as such, particularly historically, and it doesn't really make sense to grpup them in with people who worked for the company. We could use position held (P39):director (Q1162163):of (P642):[company] but not sure quite how suitable that is. Andrew Gray (talk) 11:43, 13 January 2018 (UTC)[reply]

Constraint violation (false negative)

Newsweek (Q188413) as employer (P108) results in a warning, as it needs to be a sub class of newspaper (Q11032), which is not true for Newsweek (Q188413), which is a magazine (Q41298). Either the constraint should be adapted for a higher class of „publication“ or … ? Thanks for checking. --Elya (talk) 13:24, 7 October 2018 (UTC)[reply]

Employment Sort Order

Not all employment is known at the time of recording in a database. This leads to sort-orders, where the first employment is not shown in the first place. Legibility and comprehensibility of the data-set is significantly obscured.

Is there any way to change the sort order in Property Property:P108 is other than the true temporal order? As a sample see Jason Reese. Yotwen (talk) 06:59, 30 September 2019 (UTC)[reply]

Professorship as a qualifier of Employer

Shouldn't Professorship (P803) be allowable as a qualifier under Employer? If used that way, it currently gets a constraint violation. It seems to make more sense to put this under employer than as a separate property of a person. For example:

Trisha N. Davis (Q30347547)

employer University of Washington

  start time   1 July 1994
  position held   chair
                  full professor
  professorship   Earl W. Davie/ZymoGenetics Endowed Chair in Biochemistry

This makes more sense to me than having professorship as a separate property, as the person could have held different endowed chairs at different universities.

Adam Schiff (talk) 13:23, 9 September 2020 (UTC)[reply]

Gender neutral label in French

Following this request for comments, we need to find a gender neutral label.

Since in many cases the employer is an organization, I'm not sure that it is relevant to use both male and female form ("employeur ou employeuse").

Maybe we should use a verbal form ("employé ou employée par").

What do you think? PAC2 (talk) 05:03, 18 June 2022 (UTC)[reply]

Pretty hard to understand

that "Organization" is a viable constraint, but Non-Profit organization is not. Could that be mended or explained? Yotwen (talk) 14:42, 9 March 2023 (UTC)[reply]

How to reflect gaps in employment

Possibly a silly question, but is there a way to use qualifiers to reflect (for example) someone who was employed from 2002-2012, then returned to the same employer in 2023? I tried using two start time qualifiers but it says it should only have one value. Thanks for any assistance! Emwille (talk) 20:33, 29 March 2023 (UTC)[reply]

You can simply add multiple statements. —Tacsipacsi (talk) 18:09, 30 March 2023 (UTC)[reply]

headdesk* Yep, I sure can. Thank you!

Emwille (talk) 20:17, 30 March 2023 (UTC)[reply]

Ping about discussion on Project chat

Just a note that I opened a discussion on Project chat about preferring this property as a qualifier-only on occupation (P106). Ainali (talk) 21:13, 2 December 2023 (UTC)[reply]

Conflict on dates?

Not quite sure the reason of potential conflict on dates, 1294 which seems to trigger an alert. Is it not considered part of the 13. century? See the property in Item Q8190792. Thanks for your help. jshieh (talk) 16:03, 2 February 2024 (UTC)[reply]

“13th century” is internally represented as 1300-00-00, which is obviously later than 1294-02-18, and constraints use this internal representation instead of the real value, see phab:T168379. —Tacsipacsi (talk) 13:35, 3 February 2024 (UTC)[reply]

P1416 and P108

FYI I'm currently raising some doubts regarding the current utilization of affiliation (P1416) and employer (P108) (along with other related properties) in the discussion here. I appreciate any feedback in advance. Alexmar983 (talk) 16:25, 17 February 2024 (UTC)[reply]