Triple
T36134344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971 Nebraska vs. Oklahoma football game |
E1045119
|
entity |
| Predicate | OklahomaAPRank |
P184952
|
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: [1971 Nebraska vs. Oklahoma football game, OklahomaAPRank, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OklahomaAPRank Context triple: [1971 Nebraska vs. Oklahoma football game, OklahomaAPRank, 2]
-
A.
OklahomaScore
Indicates that a score or number of points is associated with Oklahoma in a particular context or event.
-
B.
ohioStateRankAP
Indicates the ranking position assigned to Ohio State University in the Associated Press (AP) poll.
-
C.
OregonRankingCoaches
Indicates that the subject is a coach associated with Oregon and is being assigned or compared by a specific ranking among such coaches.
-
D.
MarylandAPFinalRanking
Indicates the final position assigned to Maryland in the season-ending Associated Press (AP) college sports rankings.
-
E.
OregonScore
Indicates a scoring event or point total achieved by an entity in the context of Oregon (such as a game, test, or evaluation associated with Oregon).
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b69a74a08190b31b1201278a2c57 |
completed | May 3, 2026, 8:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.