Triple
T26608524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Gators |
E667846
|
entity |
| Predicate | footballHeadCoachNotable |
P39425
|
FINISHED |
| Object | Steve Spurrier |
—
|
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: Steve Spurrier | Statement: [Florida Gators, footballHeadCoachNotable, Steve Spurrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footballHeadCoachNotable Context triple: [Florida Gators, footballHeadCoachNotable, Steve Spurrier]
-
A.
notableCoach
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
B.
notableHeadCoach
chosen
Indicates that a person has served as a head coach of particular significance or prominence for a team or organization.
-
C.
notablePlayersCoached
Indicates that a coach has trained or mentored specific players who are considered notable or distinguished in their field.
-
D.
notableFormerCoach
Indicates that an entity previously served as a coach of another entity and is recognized as particularly significant or prominent in that former coaching role.
-
E.
notableAssistantCoaches
Indicates that the subject has assistant coaches who are particularly distinguished or noteworthy in their roles.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:15 a.m.