Triple
T10759933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Morris |
E253797
|
entity |
| Predicate | thousandYardRushingSeason |
P66740
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Mercury Morris, thousandYardRushingSeason, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thousandYardRushingSeason Context triple: [Mercury Morris, thousandYardRushingSeason, 1972]
-
A.
1000YardRushingSeasons
chosen
Indicates that a player has achieved one or more seasons in which they rushed for at least 1,000 yards.
-
B.
twoThousandYardRushingSeason
Indicates that a player has achieved at least 2,000 rushing yards over the course of a single season.
-
C.
seasonsWith1500PlusRushingYards
Indicates that an entity (typically a player) has one or more seasons in which they accumulated at least 1,500 rushing yards.
-
D.
achieved1000RushingAnd1000ReceivingYardsInSeason
Indicates that a player gained at least 1,000 rushing yards and at least 1,000 receiving yards within a single season.
-
E.
rushingYards
Indicates the number of yards a player gains by running the ball on rushing plays.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72ea21c5081908babc049d0330a75 |
completed | April 9, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.