Triple
T36951151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Orange Bowl |
E914065
|
entity |
| Predicate | VirginiaTechBCSRankingEnteringGame |
P189376
|
FINISHED |
| Object | No. 3 |
—
|
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: No. 3 | Statement: [2008 Orange Bowl, VirginiaTechBCSRankingEnteringGame, No. 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VirginiaTechBCSRankingEnteringGame Context triple: [2008 Orange Bowl, VirginiaTechBCSRankingEnteringGame, No. 3]
-
A.
VirginiaTechAPRankEnteringGame
Indicates that Virginia Tech’s football team held a specific Associated Press (AP) poll ranking at the time a particular game began.
-
B.
KansasBCSRankingEnteringGame
Indicates that the predicate specifies Kansas’s BCS ranking at the time a particular game begins.
-
C.
VirginiaTechScore
Indicates the number of points scored by the Virginia Tech team in a particular game or event.
-
D.
oregonRankingEnteringGame
Indicates the ranking position held by Oregon at the time the game began.
-
E.
oregonStateRankingEnteringGame
Indicates the competitive ranking position held by Oregon State 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:13 p.m.