Triple
T34099394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1978 Gator Bowl incident |
E874521
|
entity |
| Predicate | coachInvolved |
P178415
|
FINISHED |
| Object | Woody Hayes |
—
|
NE NERFINISHED |
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: Woody Hayes | Statement: [1978 Gator Bowl incident, coachInvolved, Woody Hayes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachInvolved Context triple: [1978 Gator Bowl incident, coachInvolved, Woody Hayes]
-
A.
coachRelationship
Indicates a relationship in which one entity serves as a coach, providing guidance, training, or mentorship to another entity.
-
B.
coachOnly
Indicates that the relationship or action applies exclusively to a coach and to no other type of participant or role.
-
C.
coachProduced
Indicates that a coach was responsible for developing, training, or otherwise producing the performance or outcome associated with an entity.
-
D.
playerInvolved
Indicates that a specific player participates in, is associated with, or takes part in a particular event, action, or situation.
-
E.
coachAffiliation
Indicates that a coach is formally associated with, employed by, or represents a particular team, organization, or institution.
- F. None of above. chosen
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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:53 a.m.