Triple
T9974283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Sanders |
E196286
|
entity |
| Predicate | seasonsWith1500PlusRushingYards |
P91387
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Barry Sanders, seasonsWith1500PlusRushingYards, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonsWith1500PlusRushingYards Context triple: [Barry Sanders, seasonsWith1500PlusRushingYards, 5]
-
A.
1000YardRushingSeasons
Indicates that a player has achieved one or more seasons in which they rushed for at least 1,000 yards.
-
B.
achieved1000RushingAnd1000ReceivingYardsInSeason
Indicates that a player gained at least 1,000 rushing yards and at least 1,000 receiving yards within a single season.
-
C.
NFLAllTimeRushingYardsLeader
Indicates that the subject is the player who has accumulated the most career rushing yards in NFL history.
-
D.
singleSeasonRushingYardsRecord
Indicates the record-setting total number of rushing yards accumulated by a player in a single season.
-
E.
twoThousandYardRushingSeason
Indicates that a player has achieved at least 2,000 rushing yards over the course of a single season.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb849da448190b826cb8fbf2eeb89 |
completed | April 2, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:48 p.m.