Triple
T10839858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 World Series |
E255855
|
entity |
| Predicate | runnerUpWorldSeriesAppearancesAfterSeries |
P96009
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [1976 World Series, runnerUpWorldSeriesAppearancesAfterSeries, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpWorldSeriesAppearancesAfterSeries Context triple: [1976 World Series, runnerUpWorldSeriesAppearancesAfterSeries, 30]
-
A.
worldSeriesAppearancesAsPlayer
Indicates the number of times an individual has appeared as a player in World Series games.
-
B.
worldSeriesAppearance
Indicates that an entity (typically a team) has participated in a World Series event.
-
C.
WorldSeriesAppearance
Indicates that a team has participated in (reached and played in) a World Series championship series.
-
D.
runnerUpConsecutiveAppearances
Indicates that an entity has achieved runner-up status in a competition for a specified number of consecutive appearances or editions.
-
E.
WorldSeriesAppearanceNumberForWinner
Indicates the ordinal number of times the winning team has appeared in the World Series up to and including that instance.
- 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_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. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.