Triple
T18271242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBC Sports Premier League coverage |
E437618
|
entity |
| Predicate | includesOnDemandReplays |
P108689
|
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: [NBC Sports Premier League coverage, includesOnDemandReplays, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOnDemandReplays Context triple: [NBC Sports Premier League coverage, includesOnDemandReplays, true]
-
A.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
B.
hasReplay
chosen
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
C.
videoReplayUsed
Indicates that a video replay was utilized to review or analyze a prior event or action.
-
D.
supportsReplayProtection
Indicates that the action or system includes mechanisms to prevent replaying previously valid messages or transactions as if they were new.
-
E.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
- 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.