Triple
T16138930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Jackson |
E391602
|
entity |
| Predicate | rushingYardsWithTeam |
P121253
|
FINISHED |
| Object | St. Louis Rams over 10,000 rushing yards |
—
|
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: St. Louis Rams over 10,000 rushing yards | Statement: [Steven Jackson, rushingYardsWithTeam, St. Louis Rams over 10,000 rushing yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushingYardsWithTeam Context triple: [Steven Jackson, rushingYardsWithTeam, St. Louis Rams over 10,000 rushing yards]
-
A.
rushingYards
Indicates the number of yards a player gains by running the ball on rushing plays.
-
B.
careerRushingYards
Indicates the total number of rushing yards an entity has accumulated over the entire span of its career.
-
C.
NFLAllTimeRushingYardsLeader
Indicates that the subject is the player who has accumulated the most career rushing yards in NFL history.
-
D.
careerYardsPerCarry
Indicates the average number of yards a player gains per rushing attempt over the entirety of their career.
-
E.
nflRushingYardsLeader
Indicates the player who gained the most rushing yards in the NFL over a specified season or time period.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a06e0988190b5cd62d422d058a2 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.