Triple
T3928275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 World Series |
E93330
|
entity |
| Predicate | game6NotableEvent |
P51734
|
FINISHED |
| Object | controversial safe call at first base by umpire Don Denkinger |
—
|
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: controversial safe call at first base by umpire Don Denkinger | Statement: [1985 World Series, game6NotableEvent, controversial safe call at first base by umpire Don Denkinger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game6NotableEvent Context triple: [1985 World Series, game6NotableEvent, controversial safe call at first base by umpire Don Denkinger]
-
A.
game2NotableEvent
Indicates a notable or significant event that occurred in the context of the second game.
-
B.
notableFootballEvent
Indicates an event in football that is distinguished by particular significance, impact, or memorability within the sport.
-
C.
notableEventTeam
Indicates a team that is significantly associated with, or played a key role in, a particular notable event.
-
D.
teamInNotableEvent
Indicates that a team participated in or was involved with a notable event.
-
E.
notablePlay
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeda4f9d481908dda1b5a826ab64d |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb5f859c819095b61f5ba8eace4f |
completed | March 9, 2026, 3:46 p.m. |
Created at: March 9, 2026, 3:23 p.m.