Triple
T6694127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Brown |
E152703
|
entity |
| Predicate | singleSeasonRushingYardsLeader |
P14717
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Jim Brown, singleSeasonRushingYardsLeader, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleSeasonRushingYardsLeader Context triple: [Jim Brown, singleSeasonRushingYardsLeader, 1958]
-
A.
singleSeasonRushingYardsRecord
Indicates the record-setting total number of rushing yards accumulated by a player in a single season.
-
B.
nflRushingYardsLeader
chosen
Indicates the player who gained the most rushing yards in the NFL over a specified season or time period.
-
C.
singleSeasonRushingTouchdownsRecord
Indicates that an entity holds the record for the most rushing touchdowns scored in a single season.
-
D.
nflRushingTouchdownsLeader
Indicates the player who led all others in the number of rushing touchdowns in a given NFL season or context.
-
E.
NFLAllTimeRushingYardsLeader
Indicates that the subject is the player who has accumulated the most career rushing yards in NFL history.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.