Triple
T5848338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Fouts |
E129766
|
entity |
| Predicate | singleSeasonPassingYardsRecordHolder |
P36480
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Dan Fouts, singleSeasonPassingYardsRecordHolder, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleSeasonPassingYardsRecordHolder Context triple: [Dan Fouts, singleSeasonPassingYardsRecordHolder, 1979]
-
A.
ledNFLInPassingYards
Indicates that the subject was the league leader in total passing yards in the NFL for a given season.
-
B.
NFLRecordHeld
chosen
Indicates that one entity holds or has held a specific NFL record associated with another entity (such as a statistic, category, or achievement).
-
C.
passingYardsCareer
Indicates the total number of yards a player has gained by passing the ball over the course of their entire career.
-
D.
NFLAllTimeRushingYardsLeader
Indicates that the subject is the player who has accumulated the most career rushing yards in NFL history.
-
E.
gameWinningTouchdownPasser
Indicates that the subject is the player who threw the touchdown pass that secured the victory in the game for the subject's team.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.