Triple
T37856222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Roughnecks |
E944196
|
entity |
| Predicate | originalHeadCoach |
P20789
|
FINISHED |
| Object | June Jones |
E2244380
|
NE 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: June Jones | Statement: [Houston Roughnecks, originalHeadCoach, June Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalHeadCoach Context triple: [Houston Roughnecks, originalHeadCoach, June Jones]
-
A.
firstHeadCoach
chosen
Indicates that the referenced person served as the inaugural head coach of the specified team or organization.
-
B.
previousHeadCoach
Indicates that one entity formerly served as the head coach of the other entity before being replaced.
-
C.
headCoachFrom
Indicates that one entity serves as the head coach and originates from, or is affiliated with, the location or organization represented by the other entity.
-
D.
headCoachTo
Indicates that one entity serves as the head coach of another entity, such as a team or organization.
-
E.
eastHeadCoachTeam
Indicates that a person serves as the head coach of a team located in the Eastern division or conference.
- F. None of above.
Provenance (4 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb9808f8819083c247861d1c4cd2 |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.