Triple
T6302022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 3 |
E141277
|
entity |
| Predicate | featuresSoloVoiceType |
P2000
|
FINISHED |
| Object | alto |
—
|
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: alto | Statement: [Mahler Symphony No. 3, featuresSoloVoiceType, alto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSoloVoiceType Context triple: [Mahler Symphony No. 3, featuresSoloVoiceType, alto]
-
A.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
B.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given context.
-
C.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
D.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0645cfca88190ace060ef5b0e00e8 |
completed | March 22, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69c060e311b48190b1c74a5cf9435623 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.