Triple
T17554225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1958 World Series |
E427547
|
entity |
| Predicate | YankeesComebackFromDeficit |
P127898
|
FINISHED |
| Object | 3–1 |
—
|
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: 3–1 | Statement: [1958 World Series, YankeesComebackFromDeficit, 3–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: YankeesComebackFromDeficit Context triple: [1958 World Series, YankeesComebackFromDeficit, 3–1]
-
A.
firstMLBTeamToOvercome3–0Deficit
Indicates that the subject was the first Major League Baseball team to come back from a 3–0 series deficit to win the series.
-
B.
DodgersCameBackFromDeficit
Indicates that the Dodgers overcame a points or runs deficit to regain the lead or win the game.
-
C.
YankeesRunsSeventhInning
Indicates the number of runs scored by the Yankees in the seventh inning of a game.
-
D.
YankeesRunsEighthInning
Indicates that the New York Yankees scored a certain number of runs in the eighth inning of a game.
-
E.
ALCSDeficitOvercome
Indicates that a team has successfully come back from a losing position in an American League Championship Series (ALCS) to win the series.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45620983c81909e71f938ce934efa |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.