Triple
T1296920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL free agency |
E27673
|
entity |
| Predicate | startDateChangedReason |
P6009
|
FINISHED |
| Object | COVID-19 pandemic schedule adjustments |
—
|
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: COVID-19 pandemic schedule adjustments | Statement: [NHL free agency, startDateChangedReason, COVID-19 pandemic schedule adjustments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateChangedReason Context triple: [NHL free agency, startDateChangedReason, COVID-19 pandemic schedule adjustments]
-
A.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
B.
reasonForChange
chosen
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
E.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bee64d908190b6a9bb479959d523 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.