Triple
T28298828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amore Musica |
E713645
|
entity |
| Predicate | performerVoiceType |
P135747
|
FINISHED |
| Object | tenor |
—
|
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: tenor | Statement: [Amore Musica, performerVoiceType, tenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerVoiceType Context triple: [Amore Musica, performerVoiceType, tenor]
-
A.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
singerVoiceActor
Indicates that the subject is both a singer and a voice actor for the object, or performs voice-acting roles in addition to singing in relation to the object.
-
D.
vocalCounterpartType
Indicates the type or category of a vocal counterpart relationship that one entity has to another (e.g., spoken, sung, dubbed, narrated).
-
E.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 11:34 p.m.