Triple
T9285639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earthquake Game |
E223387
|
entity |
| Predicate | impactOnSchedule |
P26550
|
FINISHED |
| Object | delay of remainder of 1989 World Series |
—
|
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: delay of remainder of 1989 World Series | Statement: [Earthquake Game, impactOnSchedule, delay of remainder of 1989 World Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnSchedule Context triple: [Earthquake Game, impactOnSchedule, delay of remainder of 1989 World Series]
-
A.
effectOnSchedule
chosen
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
-
B.
impactIfCompleted
Indicates the effect or consequence that will occur if the referenced task or action is fully completed.
-
C.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
-
D.
schedule
Indicates that an entity arranges for an event, task, or activity to occur at a specific time or within a defined time frame.
-
E.
impactOnCaseFlow
Indicates how an event, action, or decision affects the progression, timing, or movement of cases through a process or system.
- 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_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. |
Created at: March 30, 2026, 7:35 p.m.