Triple
T6529804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inseparable |
E152200
|
entity |
| Predicate | featuresArtistVocalRange |
P1151
|
FINISHED |
| Object | whistle register |
—
|
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 | Statement: [Inseparable, featuresArtistVocalRange, whistle register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresArtistVocalRange Context triple: [Inseparable, featuresArtistVocalRange, whistle register]
-
A.
vocalRange
chosen
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.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
D.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
-
E.
vocalInfluence
Indicates that one entity affects, shapes, or modifies another entity through vocal expression, such as speech, tone, or sound.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adaafbfc8190a3e3c75ea5958c67 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.