Triple
T10839857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 World Series |
E255855
|
entity |
| Predicate | championConsecutiveWorldSeriesTitles |
P13623
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1976 World Series, championConsecutiveWorldSeriesTitles, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championConsecutiveWorldSeriesTitles Context triple: [1976 World Series, championConsecutiveWorldSeriesTitles, 2]
-
A.
numberOfWorldSeriesTitles
Indicates the count of World Series championship titles that an entity (typically a baseball team or player) has won.
-
B.
worldSeriesTitles
Indicates the number of World Series championship titles an entity (typically a baseball team) has won.
-
C.
WorldSeriesChampionships
Indicates the number of World Series championship titles that an entity (typically a baseball team or franchise) has won.
-
D.
hasWorldSeriesTitle
Indicates that an entity (typically a baseball team) has won at least one World Series championship title.
-
E.
wonBackToBackWorldSeries
chosen
Indicates that the subject team or individual won World Series championships in two consecutive years.
- F. None of above.
Provenance (3 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7470204548190ba0c724dd9367712 |
completed | April 9, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.