Triple
T6319942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1926 World Series |
E141711
|
entity |
| Predicate | cardinalsFirstWorldSeriesTitle |
P6145
|
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: [1926 World Series, cardinalsFirstWorldSeriesTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardinalsFirstWorldSeriesTitle Context triple: [1926 World Series, cardinalsFirstWorldSeriesTitle, true]
-
A.
hasWorldSeriesTitle
Indicates that an entity (typically a baseball team) has won at least one World Series championship title.
-
B.
firstWorldSeriesChampionship
chosen
Indicates that the subject entity won its first World Series championship title in the referenced season or event.
-
C.
numberOfWorldSeriesTitles
Indicates the count of World Series championship titles that an entity (typically a baseball team or player) has won.
-
D.
worldSeriesTitleAsExecutive
Indicates that an individual has won a World Series title in the role of a team executive rather than as a player or coach.
-
E.
WorldSeriesTitleWith
Indicates a relationship where two or more entities share a World Series championship title together in the same year or on the same 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c4ed7c8190bd066dc7cd3d1329 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.