Triple
T7093352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick York |
E165258
|
entity |
| Predicate | causeOfCareerInterruption |
P15987
|
FINISHED |
| Object | back injury |
—
|
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: back injury | Statement: [Dick York, causeOfCareerInterruption, back injury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfCareerInterruption Context triple: [Dick York, causeOfCareerInterruption, back injury]
-
A.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
-
B.
studCareerBegan
Indicates that a student's professional or academic career started at a specified time or institution.
-
C.
reasonForLeaving
chosen
Indicates the cause, motivation, or circumstance that led an entity to depart or discontinue an association, position, or place.
-
D.
careerImpact
Indicates how one entity influences or changes another entity’s professional trajectory, opportunities, or outcomes.
-
E.
reasonForWork
Indicates that one entity specifies the motivation, cause, or purpose behind another entity’s work or activity.
- 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_69c6887e8c10819091cee237560d32da |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e532513c8190968eea8a0d3235a0 |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.