Triple
T886873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cy Young |
E19148
|
entity |
| Predicate | earnedRunAverage |
P21408
|
FINISHED |
| Object | 2.63 |
—
|
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: 2.63 | Statement: [Cy Young, earnedRunAverage, 2.63]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedRunAverage Context triple: [Cy Young, earnedRunAverage, 2.63]
-
A.
careerEarnedRunAverage
Indicates the average number of earned runs a pitcher allows per nine innings over the entire span of their career.
-
B.
battingAverage
Indicates the statistical relationship between a batter’s number of hits and official at-bats, expressing how often they successfully get a hit.
-
C.
careerBattingAverage
Indicates the long-term batting performance of a player, calculated as their total hits divided by total at-bats over their entire career.
-
D.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
E.
clinchingHomeRunRunsBattedIn
Indicates that a particular home run both clinches a game or series and accounts for specific runs batted in (RBIs) scored by the batter.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ae774fac8190b3134d64086d65fe |
completed | March 1, 2026, 9:24 p.m. |
Created at: March 1, 2026, 7:39 p.m.