Triple
T36666256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1983 NFL season |
E905272
|
entity |
| Predicate | receivingYardsLeader |
P69375
|
FINISHED |
| Object | Wes Chandler |
—
|
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: Wes Chandler | Statement: [1983 NFL season, receivingYardsLeader, Wes Chandler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivingYardsLeader Context triple: [1983 NFL season, receivingYardsLeader, Wes Chandler]
-
A.
touchdownReceptionLeaderForTeam
Indicates the player who has recorded the most touchdown receptions for a given team.
-
B.
receptionYardsLeaderForTeam
Indicates the player who has accumulated the most receiving yards for a given team.
-
C.
ledLeagueInReceivingYards
chosen
Indicates that the subject had the highest total receiving yards in the league for a given season or time period.
-
D.
teamSeasonReceivingYardsLeader
Indicates the player who recorded the most receiving yards for a given team in a specific season.
-
E.
receptionYardsLeaderForTightEnds
Indicates the tight end who has accumulated the most receiving yards, serving as the statistical leader in that category.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:12 p.m.