Triple
T20318606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2006 NCAA Division I FBS football season |
E492148
|
entity |
| Predicate | BCSNationalChampionshipScore |
P132874
|
FINISHED |
| Object | 41–14 |
—
|
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: 41–14 | Statement: [2006 NCAA Division I FBS football season, BCSNationalChampionshipScore, 41–14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCSNationalChampionshipScore Context triple: [2006 NCAA Division I FBS football season, BCSNationalChampionshipScore, 41–14]
-
A.
BCSNationalChampionshipMVP
Indicates that the subject was selected as the Most Valuable Player of a BCS National Championship game.
-
B.
BCSNationalChampionshipVenue
Indicates the venue where the BCS National Championship game is held.
-
C.
BCSBowl
Indicates that a college football team participated in a Bowl Championship Series (BCS) bowl game in a given season or context.
-
D.
bowlGameResult
chosen
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.
NFCChampionshipGameScore
Indicates the final point totals achieved by each team in a specific NFC Championship Game matchup.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67789d8108190ae2e134f4b0b0be5 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:20 a.m.