Triple
T23680332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motetti a cinque voci |
E585000
|
entity |
| Predicate | voiceCount |
P42293
|
FINISHED |
| Object | 5 |
—
|
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 | Statement: [Motetti a cinque voci, voiceCount, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceCount Context triple: [Motetti a cinque voci, voiceCount, 5]
-
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.
hasNumberOfSpeakersCategory
Indicates a classification of an entity based on the number of speakers associated with it, typically grouping it into predefined size categories.
-
C.
hasVoices
Indicates that an entity possesses or includes one or more vocal parts, voice tracks, or spoken/sung voice elements.
-
D.
toneCount
Indicates the number of distinct tones or tonal elements associated with an entity or expression.
-
E.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f73148819089fa0c1a437f91fe |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.