Triple
T593910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 World Series |
E17335
|
entity |
| Predicate | CubsClinchingGame |
P16068
|
FINISHED |
| Object | Game 7 |
—
|
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: Game 7 | Statement: [2016 World Series, CubsClinchingGame, Game 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CubsClinchingGame Context triple: [2016 World Series, CubsClinchingGame, Game 7]
-
A.
cubsNextWorldSeriesTitle
Indicates that the Chicago Cubs will win their next World Series championship title.
-
B.
NLCSResult
Indicates the outcome or final score of a match or contest in the NLCS (National League Championship Series) between competing entities.
-
C.
cubsNextWorldSeriesAppearance
Indicates the event that is the Chicago Cubs’ next appearance in a World Series following a given reference point in time.
-
D.
ALCSResult
Indicates the outcome or result of a matchup or series in the American League Championship Series (ALCS) between the involved entities.
-
E.
WorldSeriesChampion
Indicates that a team or individual has won the championship title in a given season of the World Series.
- 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_69a49bd15c5881909b59ed4c88687e7b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.