Triple
T28968398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NCAA Division I-A football championship |
E732102
|
entity |
| Predicate | runnerUpFinalAPRank |
P67586
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1986 NCAA Division I-A football championship, runnerUpFinalAPRank, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpFinalAPRank Context triple: [1986 NCAA Division I-A football championship, runnerUpFinalAPRank, 2]
-
A.
runnerUpFinalRecord
Indicates the final performance or outcome record associated with the entity that finished as runner-up in a competition or event.
-
B.
runnerUpRank
chosen
Indicates the position or ranking assigned to an entity that finishes immediately after the winner (or near the top) in a competition or ordered list.
-
C.
runnerUpSchool
Indicates that a school finished in second place (as the runner-up) in a specified competition or event.
-
D.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
E.
runnerUpAlliance
Indicates that an alliance finished in second place in a competition or ranking.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 8:53 a.m.