Triple
T33787163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 NBA season |
E865823
|
entity |
| Predicate | reasonForScheduleChange |
P5019
|
FINISHED |
| Object | COVID-19 pandemic |
—
|
NE NERFINISHED |
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: COVID-19 pandemic | Statement: [2020–21 NBA season, reasonForScheduleChange, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForScheduleChange Context triple: [2020–21 NBA season, reasonForScheduleChange, COVID-19 pandemic]
-
A.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
B.
changeReason
chosen
Indicates the reason or justification for a modification or change made to an entity or its state.
-
C.
reasonForAppointment
Indicates the underlying purpose or cause for which an appointment is scheduled or taking place.
-
D.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
E.
rescheduled
Indicates that a previously planned event or action has been assigned a new time or date, replacing the original schedule.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:45 a.m.