Triple
T6319928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1926 World Series |
E141711
|
entity |
| Predicate | seriesClinchingScore |
P53087
|
FINISHED |
| Object | St. Louis Cardinals 3, New York Yankees 2 |
—
|
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: St. Louis Cardinals 3, New York Yankees 2 | Statement: [1926 World Series, seriesClinchingScore, St. Louis Cardinals 3, New York Yankees 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesClinchingScore Context triple: [1926 World Series, seriesClinchingScore, St. Louis Cardinals 3, New York Yankees 2]
-
A.
clinchingScore
chosen
Indicates the score or point threshold at which a participant secures a decisive or unassailable victory in a competition or contest.
-
B.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
C.
JetsScore
Indicates that the team named Jets scores a certain number of points in a game or event.
-
D.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
E.
scoredBy
Indicates that a particular score, point, or result was achieved or obtained by a specific entity.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c4ed7c8190bd066dc7cd3d1329 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.