Triple
T4076931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 World Series |
E86785
|
entity |
| Predicate | cardinalsWorldSeriesTitleNumber |
P3871
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [1967 World Series, cardinalsWorldSeriesTitleNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardinalsWorldSeriesTitleNumber Context triple: [1967 World Series, cardinalsWorldSeriesTitleNumber, 8]
-
A.
numberOfWorldSeriesTitles
Indicates the count of World Series championship titles that an entity (typically a baseball team or player) has won.
-
B.
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.
-
C.
worldSeriesTitles
chosen
Indicates the number of World Series championship titles an entity (typically a baseball team) 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.
WorldSeriesNumber
Indicates the specific sequential number assigned to a particular edition of the World Series in the overall series of championships.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.