Triple
T37724044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012 BCS National Championship Game |
E939668
|
entity |
| Predicate | BCSRankingOfNotreDameBeforeGame |
P190123
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2012 BCS National Championship Game, BCSRankingOfNotreDameBeforeGame, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCSRankingOfNotreDameBeforeGame Context triple: [2012 BCS National Championship Game, BCSRankingOfNotreDameBeforeGame, 1]
-
A.
preGameRecordOfNotreDame
Indicates the win-loss-tie record that Notre Dame held prior to a specific game or event.
-
B.
BCSRankingOfAuburnBeforeGame
Indicates the position Auburn held in the BCS rankings prior to a specific game.
-
C.
BCSRankingOfAlabamaBeforeGame
Indicates the BCS ranking position assigned to Alabama prior to a specific game being played.
-
D.
KansasBCSRankingEnteringGame
Indicates that the predicate specifies Kansas’s BCS ranking at the time a particular game begins.
-
E.
VirginiaTechBCSRankingEnteringGame
Indicates the ranking position of Virginia Tech’s Boston College Sports (BCS) standing at the time the game began.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.