Triple
T27833339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joel Spolsky |
E703159
|
entity |
| Predicate | employerAtMicrosoftRole |
P127726
|
FINISHED |
| Object | program manager |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: program manager | Statement: [Joel Spolsky, employerAtMicrosoftRole, program manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerAtMicrosoftRole Context triple: [Joel Spolsky, employerAtMicrosoftRole, program manager]
-
A.
roleAtMicrosoft
chosen
Indicates that an entity holds or held a specific role or position within Microsoft.
-
B.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
C.
sectorEmploymentRole
Indicates the specific role or function an entity holds within a particular employment sector or industry.
-
D.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
-
E.
inUniverseWorkplaceRole
Indicates that an entity holds a specific workplace role or job position within a fictional or narrative universe.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 5:57 p.m.