Triple
T7187277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American football |
E167602
|
entity |
| Predicate | popularMediaCoverage |
P29265
|
FINISHED |
| Object | television |
—
|
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 | Statement: [American football, popularMediaCoverage, television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularMediaCoverage Context triple: [American football, popularMediaCoverage, television]
-
A.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
B.
mediaCoverageAs
chosen
Indicates that one entity provides or receives media coverage in the role, capacity, or format specified by another entity.
-
C.
mediaCovered
Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
-
D.
mediaCoverageControversy
Indicates that media coverage is associated with, contributes to, or centers around a controversy involving the related entities.
-
E.
mediaCoverageFocus
Indicates the primary topic, subject, or aspect that media coverage is centered on or emphasizes.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e2506881909fc4e81b9b79e873 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.