Triple
T4106835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Headphone |
E88471
|
entity |
| Predicate | typicalContentSource |
P17306
|
FINISHED |
| Object | DVD |
—
|
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: DVD | Statement: [Dolby Headphone, typicalContentSource, DVD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContentSource Context triple: [Dolby Headphone, typicalContentSource, DVD]
-
A.
mediaOrigin
Indicates the original source or provenance from which a piece of media (such as an image, video, or audio) was derived or obtained.
-
B.
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.
-
C.
contentProvider
chosen
Indicates that one entity serves as the source or supplier of content (such as media, information, or data) for another entity.
-
D.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
E.
primaryContent
Indicates that one entity serves as the main or most important content associated with another entity.
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:40 p.m.