Triple
T22520157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geistliche Chormusik |
E556751
|
entity |
| Predicate | numberOfVoicesRange |
P42293
|
FINISHED |
| Object | 5–7 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: 5–7 voices | Statement: [Geistliche Chormusik, numberOfVoicesRange, 5–7 voices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVoicesRange Context triple: [Geistliche Chormusik, numberOfVoicesRange, 5–7 voices]
-
A.
typicalNumberOfVoices
chosen
Indicates the usual or characteristic number of distinct voices or parts involved in performing or realizing something (such as a musical work or texture).
-
B.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
C.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
D.
hasNumberOfSpeakersCategory
Indicates a classification of an entity based on the number of speakers associated with it, typically grouping it into predefined size categories.
-
E.
hasVocalRangeDescription
Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e31f43c8190899f5e35b150fe85 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.