Triple
T23374071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emotions era |
E593556
|
entity |
| Predicate | vocalFeatures |
P29850
|
FINISHED |
| Object | whistle register usage |
—
|
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: whistle register usage | Statement: [Emotions era, vocalFeatures, whistle register usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalFeatures Context triple: [Emotions era, vocalFeatures, whistle register usage]
-
A.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
B.
featuresVocoder
Indicates that one entity includes or provides a vocoder as a functional component or feature of another entity.
-
C.
featuresVocalPercussion
Indicates that the subject includes or makes use of vocal percussion (such as beatboxing or mouth-made rhythmic sounds) as part of its content or performance.
-
D.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
-
E.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b1d24881909945936cbf00876e |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.