Triple
T6456905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emotions |
E142013
|
entity |
| Predicate | vocalRangeNotedFor |
P46281
|
FINISHED |
| Object | extensive whistle register use |
—
|
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: extensive whistle register use | Statement: [Emotions, vocalRangeNotedFor, extensive whistle register use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalRangeNotedFor Context triple: [Emotions, vocalRangeNotedFor, extensive whistle register use]
-
A.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
B.
hasVocalRangeDescription
Indicates that an entity is associated with a textual description of its vocal range or vocal capabilities.
-
C.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
E.
isVocalShowcaseFor
Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d639ec8190bb0a806da4118440 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.