Triple
T18271234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBC Sports Premier League coverage |
E437618
|
entity |
| Predicate | usesWorldFeedCommentary |
P131121
|
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, usesWorldFeedCommentary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWorldFeedCommentary Context triple: [NBC Sports Premier League coverage, usesWorldFeedCommentary, true]
-
A.
usesCommentaryTeamsOf
Indicates that one entity employs or relies on the commentary teams associated with another entity for coverage or presentation.
-
B.
hasCommentaryOn
Indicates that one entity provides commentary, explanation, or evaluative remarks about another entity.
-
C.
languageOfCommentary
Indicates that one entity is the language in which the commentary on another entity is written or expressed.
-
D.
sportCommentated
Indicates that one entity provides live or recorded commentary on a sporting event involving another entity.
-
E.
coCommentatorWith
Indicates that two individuals serve together as commentators on the same event, program, or broadcast.
- 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_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. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.