Triple
T23277538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil PC2 |
E588762
|
entity |
| Predicate | supportsPolyphony |
P124957
|
FINISHED |
| Object | 64 voices |
—
|
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: 64 voices | Statement: [Kurzweil PC2, supportsPolyphony, 64 voices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPolyphony Context triple: [Kurzweil PC2, supportsPolyphony, 64 voices]
-
A.
polyphonicChannels
chosen
Indicates that an entity supports or involves multiple independent audio or musical channels that can sound simultaneously (polyphony).
-
B.
polyphony
Indicates a relationship where multiple independent melodic or vocal lines occur simultaneously, creating a layered or harmonically interwoven texture.
-
C.
supportsMultiTimbralOperation
Indicates that an entity can operate in a multi-timbral mode, handling multiple distinct timbres or instrument parts simultaneously.
-
D.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
-
E.
polyphonicSingingStyle
Indicates a singing style in which multiple independent vocal lines or melodies are performed simultaneously.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19578adf48190bdb129a55f86172c |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:49 p.m.