Triple
T19460234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 of the 2016 World Series |
E486846
|
entity |
| Predicate | CubsRunsScored |
P136005
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Game 7 of the 2016 World Series, CubsRunsScored, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CubsRunsScored Context triple: [Game 7 of the 2016 World Series, CubsRunsScored, 8]
-
A.
CubsWinningPercentage
Indicates the proportion of games that the Cubs have won relative to the total games they have played.
-
B.
CubsRegularSeasonRecord
Indicates the relationship that specifies the Chicago Cubs’ win–loss (and possibly tie) record for a particular regular baseball season.
-
C.
winTotalMLB
Indicates the total number of wins a team has achieved in Major League Baseball.
-
D.
CubsClinchingGame
Indicates the game in which the Chicago Cubs secured (clinched) a specific achievement, such as a playoff berth, division title, pennant, or championship.
-
E.
CardinalsTeamEarnedRunAverage
Indicates the earned run average statistic recorded by the Cardinals team over a specified set of games or season.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.