Triple
T30350656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-7506 |
E771979
|
entity |
| Predicate | soundIsolation |
P61641
|
FINISHED |
| Object | good passive 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: good passive isolation | Statement: [Sony MDR-7506, soundIsolation, good passive isolation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundIsolation Context triple: [Sony MDR-7506, soundIsolation, good passive isolation]
-
A.
soundInsulation
chosen
Indicates the degree to which one entity reduces or blocks the transmission of sound from another entity or environment.
-
B.
soundFocus
Indicates that attention or emphasis is directed toward a particular sound or audio source.
-
C.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
D.
soundAmplification
Indicates that one entity increases the loudness or intensity of another entity’s sound.
-
E.
soundHeardDistanceApproximate
Indicates that a sound was heard at an estimated, not precisely measured, distance from the listener or reference point.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 7:56 p.m.