Triple
T32116050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1960 NFL Championship Game |
E820240
|
entity |
| Predicate | homeTeamStarPlayer |
P173586
|
FINISHED |
| Object | Chuck Bednarik |
—
|
NE NERFINISHED |
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: Chuck Bednarik | Statement: [1960 NFL Championship Game, homeTeamStarPlayer, Chuck Bednarik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamStarPlayer Context triple: [1960 NFL Championship Game, homeTeamStarPlayer, Chuck Bednarik]
-
A.
homeTeamCaptain
Indicates that one entity serves as the captain of the home team in a given game or match in relation to the other entity.
-
B.
mostOutstandingPlayerTeam
Indicates that a team is the one for which a given player was recognized as the most outstanding (e.g., MVP) during a specific context or period.
-
C.
awayTeamCaptain
Indicates that one entity serves as the captain or designated leader of the away (visiting) team in a competition or match.
-
D.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another entity.
-
E.
homeArenaOfChampionTeam
Indicates that a particular arena serves as the primary home venue for a specified champion team.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b908810c8190bd58d2d0eee21d40 |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:28 a.m.