Triple
T9285690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 World Series |
E223389
|
entity |
| Predicate | consecutiveTitleNumberForChampion |
P87395
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1974 World Series, consecutiveTitleNumberForChampion, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecutiveTitleNumberForChampion Context triple: [1974 World Series, consecutiveTitleNumberForChampion, 3]
-
A.
consecutiveTitlesForChampion
Indicates that a champion has won multiple titles in succession without interruption.
-
B.
consecutiveTitleNumber
Indicates that one entity’s title number immediately follows another’s in a sequential ordering.
-
C.
championCityTitleNumber
Indicates the ordinal number of championship titles that a particular city has won or holds in a given competition or league.
-
D.
championshipTitleWith
Indicates a relationship where two or more entities share or are jointly associated with the same championship title.
-
E.
consecutiveLeagueTitles
Indicates that one entity has won league titles in successive seasons without interruption.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081fe8cc8190b6c1b481c7129689 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.