Triple
T19911077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vida Blue |
E478547
|
entity |
| Predicate | earnedRunAverageIn1971 |
P21408
|
FINISHED |
| Object | 1.82 |
—
|
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: 1.82 | Statement: [Vida Blue, earnedRunAverageIn1971, 1.82]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedRunAverageIn1971 Context triple: [Vida Blue, earnedRunAverageIn1971, 1.82]
-
A.
earnedRunAverage
chosen
Indicates the average number of earned runs a pitcher allows per nine innings pitched.
-
B.
earnedRunAverageLeaderSeasons
Indicates the seasons in which an entity led a league or competition in earned run average (ERA).
-
C.
earnedRunAverageTitle
Indicates that a player has received the title or recognition for having the best earned run average (ERA) in a given baseball league or season.
-
D.
careerEarnedRunAverage
Indicates the average number of earned runs a pitcher allows per nine innings over the entire span of their 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.
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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6598f31c481908a5a1d9a5656f698 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.