Triple
T12242805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turandot |
E291775
|
entity |
| Predicate | titleRoleVoiceType |
P2000
|
FINISHED |
| Object | dramatic soprano |
—
|
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: dramatic soprano | Statement: [Turandot, titleRoleVoiceType, dramatic soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleRoleVoiceType Context triple: [Turandot, titleRoleVoiceType, dramatic soprano]
-
A.
voiceActingRoleIn
Indicates that an entity performs a voice acting role in a specified work or production.
-
B.
voiceActingRole
Indicates that one entity performs the voice acting for a character or role in a work associated with the other entity.
-
C.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
-
D.
voiceActingType
Indicates the specific style or category of voice performance used in an audio-visual work or production.
-
E.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.