Triple
T2823486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riggo |
E54863
|
entity |
| Predicate | rushingYardsInNFL |
P14715
|
FINISHED |
| Object | 11000-plus |
—
|
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: 11000-plus | Statement: [Riggo, rushingYardsInNFL, 11000-plus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushingYardsInNFL Context triple: [Riggo, rushingYardsInNFL, 11000-plus]
-
A.
NFLAllTimeRushingYardsLeader
Indicates that the subject is the player who has accumulated the most career rushing yards in NFL history.
-
B.
careerRushingYards
chosen
Indicates the total number of rushing yards an entity has accumulated over the entire span of its career.
-
C.
nflRushingYardsLeader
Indicates the player who gained the most rushing yards in the NFL over a specified season or time period.
-
D.
ledNFLInPassingYards
Indicates that the subject was the league leader in total passing yards in the NFL for a given season.
-
E.
nflRushingTouchdownsLeader
Indicates the player who led all others in the number of rushing touchdowns in a given NFL season or context.
- 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.