Triple
T18271279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League fixtures |
E437619
|
entity |
| Predicate | changeReasons |
P6009
|
FINISHED |
| Object | television broadcast selections |
—
|
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: television broadcast selections | Statement: [Premier League fixtures, changeReasons, television broadcast selections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeReasons Context triple: [Premier League fixtures, changeReasons, television broadcast selections]
-
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.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
D.
changesRequirement
Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
-
E.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7e00548190a28916a696831336 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.