Triple
T24913475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football Playoff Selection Committee |
E623909
|
entity |
| Predicate | semifinalGameType |
P157227
|
FINISHED |
| Object | rotating bowl games |
—
|
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: rotating bowl games | Statement: [College Football Playoff Selection Committee, semifinalGameType, rotating bowl games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semifinalGameType Context triple: [College Football Playoff Selection Committee, semifinalGameType, rotating bowl games]
-
A.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
B.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
C.
semifinalStage
Indicates that an entity participates in or corresponds to the semifinal round of a competition or tournament.
-
D.
semifinalGamesPlayedIn
Indicates that a given semifinal game took place at or within a specified location or venue.
-
E.
officiatedGameType
Indicates the type or category of game that an official (e.g., referee or umpire) presided over.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4238ab92081908c5c8f807b2f1816 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f423637bec8190a1701421ac86a3b7 |
completed | May 1, 2026, 3:52 a.m. |
Created at: April 18, 2026, 5:28 a.m.