Triple
T20401103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randall David Johnson |
E500331
|
entity |
| Predicate | rankInMLBHistoryByStrikeouts |
P139998
|
FINISHED |
| Object | second |
—
|
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: second | Statement: [Randall David Johnson, rankInMLBHistoryByStrikeouts, second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInMLBHistoryByStrikeouts Context triple: [Randall David Johnson, rankInMLBHistoryByStrikeouts, second]
-
A.
strikeoutsLeader
Indicates that the subject is the player or entity leading others in the number of strikeouts over a specified period or context.
-
B.
strikeoutsMLB
Indicates the number of times a pitcher retires batters by strikeout in Major League Baseball.
-
C.
MVPStrikeouts
Indicates that the entity, as a Most Valuable Player (MVP), recorded a certain number of strikeouts.
-
D.
strikeoutRate
Indicates the frequency or proportion at which a pitcher (or batter) records strikeouts relative to total opportunities.
-
E.
homeRunLeaders
Indicates the relationship where certain players are identified as having the highest number of home runs, typically within a given league, season, or time span.
- F. None of above. chosen
Provenance (4 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798e7a588190b60bd54260e540f4 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:29 a.m.