Triple
T32812474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell It Like It Is |
E839191
|
entity |
| Predicate | vocalEmphasis |
P29850
|
FINISHED |
| Object | emotive vocal delivery |
—
|
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: emotive vocal delivery | Statement: [Tell It Like It Is, vocalEmphasis, emotive vocal delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalEmphasis Context triple: [Tell It Like It Is, vocalEmphasis, emotive vocal delivery]
-
A.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
B.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
C.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
D.
vocalEffects
Indicates that one entity applies or produces specific modifications, enhancements, or stylistic effects on another entity’s vocal sound or performance.
-
E.
hasEmotiveVocals
Indicates that the subject produces vocals characterized by strong or expressive emotion.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:15 a.m.