Triple
T37358771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fin ch’han dal vino |
E927523
|
entity |
| Predicate | voiceTypeOfCharacter |
P190102
|
FINISHED |
| Object | baritone |
—
|
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: baritone | Statement: [Fin ch’han dal vino, voiceTypeOfCharacter, baritone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceTypeOfCharacter Context triple: [Fin ch’han dal vino, voiceTypeOfCharacter, baritone]
-
A.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
voiceCharacter
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
C.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
D.
roleInTheVoices
Indicates that an entity has a specific role or participation in the production or performance of "The Voices."
-
E.
voiceTypeOfCharacter Polinesso
Indicates that the specified voice type is the vocal classification assigned to the character Polinesso.
- F. None of above. chosen
Provenance (4 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:16 p.m.