Triple
T36950332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary Pinkel era |
E914043
|
entity |
| Predicate | bowlGameType |
P133750
|
FINISHED |
| Object | New Year’s Day 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: New Year’s Day bowl games | Statement: [Gary Pinkel era, bowlGameType, New Year’s Day bowl games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlGameType Context triple: [Gary Pinkel era, bowlGameType, New Year’s Day bowl games]
-
A.
bowlGame
Indicates that the relationship or event involves a postseason college football bowl game in which a team participates or that is associated with an entity.
-
B.
hasBowlGameType
chosen
Indicates that an entity’s associated bowl game is of a specified type or category.
-
C.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
D.
bowlGameResult
Indicates the outcome of a specific bowl game, typically linking the game to the competing teams and the final result (such as winner, loser, and score).
-
E.
officiatedGameType
Indicates the type or category of game that an official (e.g., referee or umpire) presided over.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.