Triple
T30390206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doug Dorsey |
E773058
|
entity |
| Predicate | reasonForCareerChange |
P6009
|
FINISHED |
| Object | loss of peripheral vision |
—
|
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: loss of peripheral vision | Statement: [Doug Dorsey, reasonForCareerChange, loss of peripheral vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCareerChange Context triple: [Doug Dorsey, reasonForCareerChange, loss of peripheral vision]
-
A.
endCauseOfCareer
Indicates that one entity is the cause or reason for another entity’s career coming to an end.
-
B.
reasonForLeaving
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
C.
occupationalChange
Indicates a change in a person’s job, profession, or occupational status over time.
-
D.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
E.
laterCareerInterest
Indicates that an entity develops or expresses interest in a particular career or professional field at a later stage in time, relative to an earlier period or context.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 8:02 p.m.