Triple
T20748176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1955 MLB All-Star Game |
E510643
|
entity |
| Predicate | comebackWin |
P141347
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1955 MLB All-Star Game, comebackWin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comebackWin Context triple: [1955 MLB All-Star Game, comebackWin, true]
-
A.
madeComeback
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
B.
comebackContext
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
-
C.
comebackSingleFor
Indicates that a particular single serves as a comeback release for an artist or group, marking their return after a hiatus or previous work.
-
D.
decidingGameComebackWin
Indicates that a team or player secured a win in the final, decisive game of a series by overcoming a deficit and mounting a comeback.
-
E.
comebackToScore
Indicates that an entity returns or recovers in a competition or contest and succeeds in scoring after previously being behind or scoreless.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:33 p.m.