Triple
T9793874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rickey Henderson |
E237669
|
entity |
| Predicate | careerRunsScoredRecord |
P29425
|
FINISHED |
| Object | 2295 career runs scored |
—
|
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: 2295 career runs scored | Statement: [Rickey Henderson, careerRunsScoredRecord, 2295 career runs scored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careerRunsScoredRecord Context triple: [Rickey Henderson, careerRunsScoredRecord, 2295 career runs scored]
-
A.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
B.
leadingRunScorer
Indicates that the subject is the player who has scored the most runs (the top run-scorer) in a given match, series, tournament, or season.
-
C.
earnedRunAverageLeaderSeasons
Indicates the seasons in which an entity led a league or competition in earned run average (ERA).
-
D.
careerRuns
Indicates the total number of runs a player has scored over the entire duration of their professional career.
-
E.
isAllTimeRecordHolderFor
chosen
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda347b6bc8190a99b7dec1650cd46 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.