Triple
T36951149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Orange Bowl |
E914065
|
entity |
| Predicate | VirginiaTechAPRankEnteringGame |
P188929
|
FINISHED |
| Object | No. 5 |
—
|
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. 5 | Statement: [2008 Orange Bowl, VirginiaTechAPRankEnteringGame, No. 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VirginiaTechAPRankEnteringGame Context triple: [2008 Orange Bowl, VirginiaTechAPRankEnteringGame, No. 5]
-
A.
VirginiaTechScore
Indicates the number of points scored by the Virginia Tech team in a particular game or event.
-
B.
VirginiaTechSeasonRecordBeforeBowl
Indicates the win-loss (and possibly tie) record of the Virginia Tech football team for a given season prior to playing its bowl game.
-
C.
VirginiaTechSeasonRecordAfterBowl
Indicates the overall win-loss record of the Virginia Tech football team for a given season, including the result of its bowl game.
-
D.
oregonRankingEnteringGame
Indicates the ranking position held by Oregon at the time the game began.
-
E.
VirginiaTechConference
Indicates a conference event associated with or hosted by Virginia Tech.
- 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_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:13 p.m.