Triple
T30924954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. R. Richard |
E787830
|
entity |
| Predicate | ledLeagueInStrikeouts |
P30679
|
FINISHED |
| Object | 1978 |
—
|
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: 1978 | Statement: [J. R. Richard, ledLeagueInStrikeouts, 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledLeagueInStrikeouts Context triple: [J. R. Richard, ledLeagueInStrikeouts, 1978]
-
A.
ledLeagueInHitByPitch
Indicates that the subject led a league in the number of times they were hit by a pitch during a given season or period.
-
B.
strikeoutsMLB
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
C.
strikeoutsLeader
chosen
Indicates that the subject is the player or entity leading others in the number of strikeouts over a specified period or context.
-
D.
ledLeagueInPlateAppearances
Indicates that the subject had the highest number of plate appearances in the league for a given season or time period.
-
E.
ledLeagueInHomeRuns
Indicates that the subject achieved the highest number of home runs in a particular league over a specified season or time period.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692b82df881909350359a39daa9ff |
completed | May 3, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:51 p.m.