Triple
T19148561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violetta Valéry |
E468744
|
entity |
| Predicate | vocalDemand |
P40358
|
FINISHED |
| Object | wide vocal range |
—
|
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: wide vocal range | Statement: [Violetta Valéry, vocalDemand, wide vocal range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalDemand Context triple: [Violetta Valéry, vocalDemand, wide vocal range]
-
A.
vocalRequirement
chosen
Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
-
B.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
C.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
-
D.
vocalInfluence
Indicates that one entity affects, shapes, or modifies another entity through vocal expression, such as speech, tone, or sound.
-
E.
vocalTraining
Indicates that one entity provides or engages in training aimed at improving another entity’s vocal or singing abilities.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97b48508190b61458821b6475ad |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.