Triple
T32114205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony Dynamic Digital Sound |
E820193
|
entity |
| Predicate | audioPresentation |
P81859
|
FINISHED |
| Object | cinema surround sound |
—
|
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: cinema surround sound | Statement: [Sony Dynamic Digital Sound, audioPresentation, cinema surround sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioPresentation Context triple: [Sony Dynamic Digital Sound, audioPresentation, cinema surround sound]
-
A.
audioStyle
chosen
Indicates the manner or characteristics of how audio is presented, performed, or produced in relation to an entity.
-
B.
audioApplication
Indicates that an entity is an application whose primary function involves processing, playing, recording, or otherwise handling audio content.
-
C.
audibleIn
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
D.
audioMedium
Indicates that something is conveyed, stored, or presented through an audio-based medium or format.
-
E.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b906a92c819096335394dd7f767e |
completed | May 3, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:28 a.m.