Triple
T470051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1905 World Series |
E8534
|
entity |
| Predicate | allGamesCompleteGameShutouts |
P15134
|
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: [1905 World Series, allGamesCompleteGameShutouts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allGamesCompleteGameShutouts Context triple: [1905 World Series, allGamesCompleteGameShutouts, true]
-
A.
featuresExtraInningGames
Indicates that the subject includes or contains games that extend beyond the standard number of innings (extra-inning games).
-
B.
seriesWinningGame
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
C.
numberOfGamesScheduled
Indicates the total count of games that have been planned or arranged for a given entity or time period.
-
D.
finalMLBSeason
Indicates the specific MLB season that was the last one in which the subject participated or was active.
-
E.
game2WinningPitcher
Indicates that one entity is the pitcher who earned the win in the second game of a series or event for the other entity.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.