Triple
T6568148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Schaub |
E153964
|
entity |
| Predicate | seasonLedLeagueInPassingYards |
P18817
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Matt Schaub, seasonLedLeagueInPassingYards, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonLedLeagueInPassingYards Context triple: [Matt Schaub, seasonLedLeagueInPassingYards, 2009]
-
A.
ledNFLInPassingYards
chosen
Indicates that the subject was the league leader in total passing yards in the NFL for a given season.
-
B.
ledNFLInPassingTouchdowns
Indicates that the subject was the league leader in passing touchdowns in the NFL for a given season or time period.
-
C.
ledLeagueInReceivingYards
Indicates that the subject had the highest total receiving yards in the league for a given season or time period.
-
D.
nflRushingYardsLeader
Indicates the player who gained the most rushing yards in the NFL over a specified season or time period.
-
E.
singleSeasonRushingYardsRecord
Indicates the record-setting total number of rushing yards accumulated by a player in a single season.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.