Triple
T12404522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 World Series |
E296346
|
entity |
| Predicate | YankeesWorldSeriesAppearancesAfterSeries |
P24502
|
FINISHED |
| Object | 36 |
—
|
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: 36 | Statement: [1999 World Series, YankeesWorldSeriesAppearancesAfterSeries, 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: YankeesWorldSeriesAppearancesAfterSeries Context triple: [1999 World Series, YankeesWorldSeriesAppearancesAfterSeries, 36]
-
A.
YankeesConsecutiveTitles
Indicates that the New York Yankees won championship titles in consecutive seasons.
-
B.
WorldSeriesAppearanceNumberForWinner
chosen
Indicates the ordinal number of times the winning team has appeared in the World Series up to and including that instance.
-
C.
WorldSeriesAppearance
Indicates that a team has participated in (reached and played in) a World Series championship series.
-
D.
worldSeriesAppearance
Indicates that an entity (typically a team) has participated in a World Series event.
-
E.
redSoxWorldSeriesAppearanceNumber
Indicates the ordinal number of a particular World Series appearance made by the Boston Red Sox.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.