Triple
T36134353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1971 Nebraska vs. Oklahoma football game |
E1045119
|
entity |
| Predicate | notablePlayerNebraska |
P10392
|
FINISHED |
| Object | Johnny Rodgers |
E320858
|
NE 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: Johnny Rodgers | Statement: [1971 Nebraska vs. Oklahoma football game, notablePlayerNebraska, Johnny Rodgers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerNebraska Context triple: [1971 Nebraska vs. Oklahoma football game, notablePlayerNebraska, Johnny Rodgers]
-
A.
notableBowlParticipant
Indicates that an entity has participated in a bowl game in a way considered notable or significant.
-
B.
notableAthlete
chosen
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
C.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
D.
notableHallOfFamer
Indicates that the subject is recognized as a particularly distinguished or prominent member of a hall of fame.
-
E.
notableLinebacker
Indicates that the subject is a linebacker who is particularly prominent, distinguished, or well-recognized in that role.
- F. None of above.
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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38de1767908190a8187a2d31e65422 |
completed | June 22, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.