Triple
T38685606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Dawkins |
E949107
|
entity |
| Predicate | previousCoachPosition |
P58548
|
FINISHED |
| Object | assistant coach |
—
|
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: assistant coach | Statement: [Johnny Dawkins, previousCoachPosition, assistant coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousCoachPosition Context triple: [Johnny Dawkins, previousCoachPosition, assistant coach]
-
A.
coachPreviousPosition
chosen
Indicates that a coach previously held a specific position or role before their current one.
-
B.
previousHeadCoach
Indicates that one entity formerly served as the head coach of the other entity before being replaced.
-
C.
subsequentCoachPosition
Indicates that one coaching position held by an individual occurs chronologically after another coaching position held by the same individual.
-
D.
former coach
Indicates that one entity previously served as the coach of another entity but no longer holds that position.
-
E.
coachesPosition
Indicates that one entity serves as the coach for a specific position or role associated with another entity.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 3, 2026, 4:33 p.m.