Triple
T29521435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Michigan Broncos football |
E748945
|
entity |
| Predicate | 2016BowlGame |
P166993
|
FINISHED |
| Object | Cotton Bowl Classic |
—
|
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: Cotton Bowl Classic | Statement: [Western Michigan Broncos football, 2016BowlGame, Cotton Bowl Classic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2016BowlGame Context triple: [Western Michigan Broncos football, 2016BowlGame, Cotton Bowl Classic]
-
A.
BCSBowl
Indicates that a college football team participated in a Bowl Championship Series (BCS) bowl game in a given season or context.
-
B.
lastSeasonAsGoDaddyBowl
Indicates the season in which a particular event or game was last held under the name "GoDaddy Bowl."
-
C.
roseBowlOpponentForWinner
Indicates the team that was defeated by the winning team in the Rose Bowl game.
-
D.
NCAAFinalRunnerUp
Indicates that an entity finished in second place (as the runner-up) in the NCAA football championship for a given season.
-
E.
roseBowlNumber
Indicates the specific edition or sequence number assigned to a particular Rose Bowl game within the series of all Rose Bowl games.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9973b08190bbb12bd759f0578e |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:41 p.m.