Triple
T37359156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voi che sapete |
E927532
|
entity |
| Predicate | characterVoiceCasting |
P201298
|
FINISHED |
| Object | female singer in trouser role |
—
|
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: female singer in trouser role | Statement: [Voi che sapete, characterVoiceCasting, female singer in trouser role]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterVoiceCasting Context triple: [Voi che sapete, characterVoiceCasting, female singer in trouser role]
-
A.
voiceCharacter
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
B.
voiceline
Indicates that one entity is an audio line or spoken phrase associated with another entity, such as a character, event, or situation.
-
C.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
D.
voiceActingType
Indicates the specific style or category of voice performance used in an audio-visual work or production.
-
E.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
- 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_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
| PDg | Predicate description generation | batch_69ffe6e21f748190a18dfe0878d397f7 |
completed | May 10, 2026, 2:01 a.m. |
Created at: May 3, 2026, 4:16 p.m.