Triple
T33660688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1986 NFC Championship Game |
E862342
|
entity |
| Predicate | homeTeamTightEnd |
P178376
|
FINISHED |
| Object | Mark Bavaro |
—
|
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: Mark Bavaro | Statement: [1986 NFC Championship Game, homeTeamTightEnd, Mark Bavaro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamTightEnd Context triple: [1986 NFC Championship Game, homeTeamTightEnd, Mark Bavaro]
-
A.
DenverBroncosTightEnd
Indicates that the subject is a tight end who plays (or played) for the Denver Broncos football team.
-
B.
startingTightEnd
Indicates that an entity serves as the primary tight end at the start of a game, play, season, or lineup configuration.
-
C.
homeTeamKicker
Indicates that the specified kicker is the primary placekicker for the home team in a game or match.
-
D.
receptionYardsLeaderForTightEnds
Indicates the tight end who has accumulated the most receiving yards, serving as the statistical leader in that category.
-
E.
awayTeamKicker
Indicates the player who serves as the kicker for the away team in a game or match.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:42 a.m.