Triple
T26208682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2–0 Dodgers |
E655423
|
entity |
| Predicate | championshipClinched |
P43074
|
FINISHED |
| Object | 1965 World Series title |
—
|
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: 1965 World Series title | Statement: [2–0 Dodgers, championshipClinched, 1965 World Series title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipClinched Context triple: [2–0 Dodgers, championshipClinched, 1965 World Series title]
-
A.
championshipOutcome
Indicates the result or final standing of a competitor or team in a championship event.
-
B.
clinchedInGame
Indicates that a team or player secured a decisive outcome (such as winning a series, title, or advancement) specifically in that particular game.
-
C.
championshipStatus
Indicates the competitive or title-holding state of an entity within a championship or league context.
-
D.
championshipGame
Indicates a game that determines the overall champion or winner of a competition or tournament.
-
E.
clinchedBy
chosen
Indicates that a particular outcome, title, or achievement has been definitively secured or guaranteed by a specific entity.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:51 p.m.