Triple
T24688124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 National League Championship Series |
E611352
|
entity |
| Predicate | winnerWonWorldSeries |
P2175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1976 National League Championship Series, winnerWonWorldSeries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerWonWorldSeries Context triple: [1976 National League Championship Series, winnerWonWorldSeries, true]
-
A.
WorldSeriesChampion
chosen
Indicates that a team or individual has won the championship title in a given season of the World Series.
-
B.
wonWorldSeriesAgainst
Indicates that one team became the World Series champion by defeating another specific team in the championship series.
-
C.
resultingWorldSeries
Indicates the specific World Series event or outcome that results from a given preceding condition, season, or set of circumstances.
-
D.
worldSeriesResultForALChampion
Indicates the outcome of a World Series for a given American League (AL) champion team.
-
E.
wonWorldSeriesWithTeam
Indicates that a person achieved a World Series championship as a member of a specified team.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:19 a.m.