Triple
T8885517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Speak Six Languages |
E211518
|
entity |
| Predicate | typicalPerformerVoiceType |
P2000
|
FINISHED |
| Object | female vocal |
—
|
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 vocal | Statement: [I Speak Six Languages, typicalPerformerVoiceType, female vocal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformerVoiceType Context triple: [I Speak Six Languages, typicalPerformerVoiceType, female vocal]
-
A.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
speakerType
Indicates the role or category of a participant in a communicative act (e.g., narrator, quoted speaker, system voice) within a given context.
-
C.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
typicalNumberOfVoices
Indicates the usual or characteristic number of distinct voices or parts involved in performing or realizing something (such as a musical work or texture).
-
E.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618bd30881909e54d0708f144786 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.