Triple
T32015963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaston (song) |
E817539
|
entity |
| Predicate | primaryVocalRange |
P1151
|
FINISHED |
| Object | baritone lead |
—
|
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: baritone lead | Statement: [Gaston (song), primaryVocalRange, baritone lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVocalRange Context triple: [Gaston (song), primaryVocalRange, baritone lead]
-
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.
primaryInstrumentalVoice
Indicates that one entity serves as the main instrumental or musical voice through which another entity is expressed, performed, or realized.
-
D.
primaryVocalist
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
-
E.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:16 a.m.