Triple
T6664862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anderson Cooper 360° |
E151572
|
entity |
| Predicate | coveredMedium |
P5765
|
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: [Anderson Cooper 360°, coveredMedium, television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredMedium Context triple: [Anderson Cooper 360°, coveredMedium, television]
-
A.
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.
-
B.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
C.
mediaExposure
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
-
D.
secondaryMedium
Indicates that an entity is associated with an additional, non-primary medium or channel through which it is expressed, delivered, or communicated.
-
E.
primaryMedium
chosen
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.