Triple
T9184876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1911 World Series |
E220431
|
entity |
| Predicate | gameInterruptedBy |
P12074
|
FINISHED |
| Object | stadium fire at Polo Grounds |
—
|
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: stadium fire at Polo Grounds | Statement: [1911 World Series, gameInterruptedBy, stadium fire at Polo Grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameInterruptedBy Context triple: [1911 World Series, gameInterruptedBy, stadium fire at Polo Grounds]
-
A.
gameInterrupted
chosen
Indicates that an ongoing game has been stopped or disrupted before reaching its normal conclusion.
-
B.
wasInterruptedBy
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
C.
game6CrucialErrorPlayer
Indicates that a player committed a crucial error in game 6.
-
D.
constructionInterruptedBy
Indicates that an ongoing construction process is halted, delayed, or disrupted due to the actions or occurrence of another specified entity or event.
-
E.
reignInterrupted
Indicates that a ruler’s period of governance was broken by one or more interruptions rather than being continuous.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc318d5c081908c50b56e5783ea38 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.