Triple
T32116107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Taylor |
E820241
|
entity |
| Predicate | rushingYardsIn1962Season |
P52812
|
FINISHED |
| Object | 1474 |
—
|
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: 1474 | Statement: [Jim Taylor, rushingYardsIn1962Season, 1474]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rushingYardsIn1962Season Context triple: [Jim Taylor, rushingYardsIn1962Season, 1474]
-
A.
rushingYards
chosen
Indicates the number of yards a player gains by running the ball on rushing plays.
-
B.
rushingYardsRecord
Indicates that an entity holds or represents the record for the greatest number of rushing yards achieved in a specified context (such as a game, season, or career).
-
C.
rushingYardsWithTeam
Indicates the number of rushing yards a player gained while playing for a specific team.
-
D.
rushingYardsLeaderSeasons
Indicates the seasons in which a given player led a league or competition in total rushing yards.
-
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.
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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b908810c8190bd58d2d0eee21d40 |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.