Triple
T34721712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby S noise reduction |
E1000933
|
entity |
| Predicate | performanceApproaches |
P23715
|
FINISHED |
| Object | Dolby SR |
—
|
NE NERFINISHED |
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: Dolby SR | Statement: [Dolby S noise reduction, performanceApproaches, Dolby SR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceApproaches Context triple: [Dolby S noise reduction, performanceApproaches, Dolby SR]
-
A.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving another entity.
-
B.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
-
C.
performanceBasis
Indicates that one entity’s performance is evaluated, determined, or justified on the basis of another specified factor, standard, or reference.
-
D.
approaches
chosen
Indicates that one entity moves closer in position or state to another entity or reference point.
-
E.
performanceIncludes
Indicates that a performance encompasses, contains, or is composed of a specified component, act, segment, or element.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 3, 2026, 3:59 p.m.