Triple
T33233859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 AFC Championship Game |
E850773
|
entity |
| Predicate | visitorTeamQuarterback |
P20576
|
FINISHED |
| Object | Dan Fouts |
—
|
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: Dan Fouts | Statement: [1981 AFC Championship Game, visitorTeamQuarterback, Dan Fouts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorTeamQuarterback Context triple: [1981 AFC Championship Game, visitorTeamQuarterback, Dan Fouts]
-
A.
opponentQuarterback
Indicates that one entity is the quarterback playing for the opposing team relative to the other entity.
-
B.
featuredQuarterback
Indicates that an entity serves as the primary or highlighted quarterback in a particular context, such as a game, season, or team promotion.
-
C.
JetsQuarterback
Indicates that the subject is a quarterback who plays for, or is associated with, the New York Jets football team.
-
D.
quarterback
chosen
Indicates that an entity performs the role or action of playing as the quarterback in a football context for another entity (such as a team).
-
E.
homeTeamQuarterbackStarter
Indicates that the specified quarterback is the starting quarterback for the home team in a given game or event.
- F. None of above.
Provenance (3 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:31 a.m.