Triple
T31003012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 MLB All-Star Game |
E789989
|
entity |
| Predicate | reasonForRescheduling |
P18029
|
FINISHED |
| Object | players strike |
—
|
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: players strike | Statement: [1981 MLB All-Star Game, reasonForRescheduling, players strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRescheduling Context triple: [1981 MLB All-Star Game, reasonForRescheduling, players strike]
-
A.
reasonForAppointment
Indicates the underlying purpose or cause for which an appointment is scheduled or taking place.
-
B.
postponementReason
chosen
Indicates the reason or cause for which an event, action, or decision has been delayed or rescheduled.
-
C.
rescheduled
Indicates that a previously planned event or action has been assigned a new time or date, replacing the original schedule.
-
D.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
E.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:57 p.m.