Triple
T31003011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 MLB All-Star Game |
E789989
|
entity |
| Predicate | rescheduled |
P170896
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1981 MLB All-Star Game, rescheduled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescheduled Context triple: [1981 MLB All-Star Game, rescheduled, true]
-
A.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
-
B.
rescheduledVenue
Indicates that the location or venue for an event or activity has been changed from its original setting to a new one as part of a rescheduling.
-
C.
postponedFrom
Indicates that an event or action has been rescheduled to occur at a later time than originally planned.
-
D.
scheduledAs
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
E.
scheduledBy
Indicates that an event, task, or appointment has been arranged or planned by a particular agent or entity.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:57 p.m.