Triple
T7289131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yours Truly |
E163947
|
entity |
| Predicate | vocalStyleFeatures |
P29850
|
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: [Yours Truly, vocalStyleFeatures, whistle register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalStyleFeatures Context triple: [Yours Truly, vocalStyleFeatures, whistle register]
-
A.
vocalizationCharacteristic
chosen
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
B.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
C.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
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.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given context.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb6bde448190b52852c916a8059d |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.