Triple
T28968394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NCAA Division I-A football championship |
E732102
|
entity |
| Predicate | championFinalRecord |
P134518
|
FINISHED |
| Object | 12–0 |
—
|
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: 12–0 | Statement: [1986 NCAA Division I-A football championship, championFinalRecord, 12–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championFinalRecord Context triple: [1986 NCAA Division I-A football championship, championFinalRecord, 12–0]
-
A.
championFinalsRecord
Indicates the win–loss record a champion has specifically in finals appearances.
-
B.
championWinLossRecord
chosen
Indicates the win–loss performance record of a champion in competitive contexts.
-
C.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
D.
championRegularSeasonRecord
Indicates that an entity is the champion associated with a particular regular season record.
-
E.
championRegularSeasonWins
Indicates that an entity is the champion based on having the highest number of regular season wins.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:53 a.m.