Triple
T30144835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murchunga |
E766226
|
entity |
| Predicate | intonationControl |
P78031
|
FINISHED |
| Object | by changing mouth shape and breath |
—
|
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: by changing mouth shape and breath | Statement: [Murchunga, intonationControl, by changing mouth shape and breath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intonationControl Context triple: [Murchunga, intonationControl, by changing mouth shape and breath]
-
A.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
B.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
D.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
E.
pitchAlterationMechanism
chosen
Indicates the mechanism or method by which the pitch of a sound or signal is changed or controlled.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8b21048190b0fbccb10b2d3523 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:18 p.m.