Triple
T15223872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1968 World Series |
E363826
|
entity |
| Predicate | game1Shutout |
P117604
|
FINISHED |
| Object | St. Louis Cardinals 4–0 Detroit Tigers |
—
|
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 4–0 Detroit Tigers | Statement: [1968 World Series, game1Shutout, St. Louis Cardinals 4–0 Detroit Tigers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game1Shutout Context triple: [1968 World Series, game1Shutout, St. Louis Cardinals 4–0 Detroit Tigers]
-
A.
game6CompleteGameShutoutPitcher
Indicates that the pitcher threw a complete game in game 6 without allowing the opposing team to score any runs.
-
B.
teamInGame7Shutout
Indicates that a team participated in a Game 7 and did not allow the opposing team to score any points.
-
C.
opponentInGame7Shutout
Indicates that one entity was the opposing team or player in a Game 7 that resulted in a shutout.
-
D.
shutouts
Indicates that one participant prevents the opposing side from scoring any points during a game or contest.
-
E.
allGamesCompleteGameShutouts
Indicates that every game in the relevant set was a complete game in which the opposing team was held scoreless (a shutout).
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078a9318819081db3b7bcc28e04f |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.