Triple
T595479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1908 World Series |
E17371
|
entity |
| Predicate | CubsChampionshipDroughtEndYear |
P15864
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [1908 World Series, CubsChampionshipDroughtEndYear, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CubsChampionshipDroughtEndYear Context triple: [1908 World Series, CubsChampionshipDroughtEndYear, 2016]
-
A.
cubsNextWorldSeriesAppearance
Indicates the event that is the Chicago Cubs’ next appearance in a World Series following a given reference point in time.
-
B.
cubsNextWorldSeriesTitle
Indicates that the Chicago Cubs will win their next World Series championship title.
-
C.
redSoxChampionshipDroughtStartYear
Indicates the year in which the Boston Red Sox’s championship drought began.
-
D.
firstWorldSeriesChampionship
Indicates that the subject entity won its first World Series championship title in the referenced season or event.
-
E.
tripleCrownYear
Indicates the year in which an entity achieved a Triple Crown title or completed a Triple Crown accomplishment.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd280ac8190b6a530ce73da85c8 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494ceeb7881909a91ed1a35d5bf0a |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985b7d7481909b5d30f4001ed61c |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.