Triple
T30384033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-V6 |
E772899
|
entity |
| Predicate | noiseIsolation |
P107588
|
FINISHED |
| Object | passive noise isolation |
—
|
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: passive noise isolation | Statement: [Sony MDR-V6, noiseIsolation, passive noise isolation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noiseIsolation Context triple: [Sony MDR-V6, noiseIsolation, passive noise isolation]
-
A.
noiseReductionFeature
Indicates that an entity includes or supports a capability to reduce or minimize unwanted noise.
-
B.
noiseReductionType
chosen
Indicates the specific method or technique used to reduce or minimize noise in a given context.
-
C.
noiseLevel
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
D.
noiseCompliance
Indicates that an entity adheres to specified rules or standards governing acceptable noise levels or sound emissions.
-
E.
noisePolicy
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:01 p.m.