Triple
T37620270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 BCS National Championship |
E936047
|
entity |
| Predicate | AuburnLeadingAtHalftime |
P11635
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2013 BCS National Championship, AuburnLeadingAtHalftime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AuburnLeadingAtHalftime Context triple: [2013 BCS National Championship, AuburnLeadingAtHalftime, true]
-
A.
homeTeamPointsInFirstHalf
Indicates the number of points scored by the home team during the first half of a game.
-
B.
awayTeamPointsInFirstHalf
Indicates the number of points scored by the away team during the first half of a game.
-
C.
halftimeScore
chosen
Indicates the score or result of a game or match at the halfway point (halftime).
-
D.
halfInning
Indicates the specific offensive or defensive segment of an inning in a game, typically distinguishing the top (visiting team at bat) from the bottom (home team at bat).
-
E.
IndianaSemifinalOpponent
Indicates that one entity is the opponent that another entity faced in a semifinal match held in Indiana.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.