Triple
T21527919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missa Ultimi miei sospiri |
E531144
|
entity |
| Predicate | voicing |
P125166
|
FINISHED |
| Object | a cappella choir |
—
|
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: a cappella choir | Statement: [Missa Ultimi miei sospiri, voicing, a cappella choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voicing Context triple: [Missa Ultimi miei sospiri, voicing, a cappella choir]
-
A.
hasVoicing
chosen
Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
-
B.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
C.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
D.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
E.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88522e948190b9fa5a3587f32eae |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.