Triple
T38338133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1939 World Series |
E1038016
|
entity |
| Predicate | championPreviousTitle |
P24479
|
FINISHED |
| Object | 1938 World Series |
—
|
NE NERFINISHED |
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: 1938 World Series | Statement: [1939 World Series, championPreviousTitle, 1938 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championPreviousTitle Context triple: [1939 World Series, championPreviousTitle, 1938 World Series]
-
A.
championLastTitleBefore
Indicates that one entity won its most recent championship title before the time or event associated with the other entity.
-
B.
championPreviousTitleYear
Indicates the year in which the current champion previously held the same title.
-
C.
championPreviousTitleSeason
chosen
Indicates that an entity was the champion of the immediately preceding season for a given title or competition.
-
D.
worldChampionPredecessor
Indicates that one entity was the immediate previous world champion before another entity.
-
E.
notableFormerChampion
Indicates that an entity was once a champion of something and is recognized as particularly distinguished or prominent in that former champion role.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:30 p.m.