Triple
T16462036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-70 Series |
E399828
|
entity |
| Predicate | Game6Controversy |
P51734
|
FINISHED |
| Object | missed call at first base in the 9th inning |
—
|
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: missed call at first base in the 9th inning | Statement: [I-70 Series, Game6Controversy, missed call at first base in the 9th inning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Game6Controversy Context triple: [I-70 Series, Game6Controversy, missed call at first base in the 9th inning]
-
A.
game6ControversyPlayPitcher
Indicates that a specific play in game 6 was controversial and involved a particular pitcher.
-
B.
game6ControversyPlayBatter
Indicates that a specific controversial play in game 6 involved a particular batter as the offensive participant.
-
C.
game6NotableEvent
chosen
Indicates that a notable event occurred during game 6 of a series or competition involving the related entities.
-
D.
controversialBecause
Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
-
E.
controversyType
Indicates the specific kind or category of controversy associated with an entity or situation.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d819d548190bc76a0ec2e223437 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.