Triple
T18188682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlophone PMC 1240 (mono) |
E435477
|
entity |
| Predicate | isMonoMixDistinctFromStereo |
P130155
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parlophone PMC 1240 (mono), isMonoMixDistinctFromStereo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonoMixDistinctFromStereo Context triple: [Parlophone PMC 1240 (mono), isMonoMixDistinctFromStereo, true]
-
A.
hasStereoOutput
Indicates that an entity provides or supports audio output in stereo (two-channel) format.
-
B.
supportsDownmixing
Indicates that one entity can convert or mix multi-channel audio into a format with fewer channels (e.g., surround sound to stereo).
-
C.
stereoCapability
Indicates that an entity has the ability to produce, process, or support stereo (two-channel) audio.
-
D.
usesSeparateChannelFor
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
E.
isMonotherapy
Indicates that a treatment is used alone, without being combined with any other therapies.
- F. None of above. chosen
Provenance (4 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e00059d4819097f681e702fe49e6 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.