Triple
T6330086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahler Symphony No. 8 |
E141955
|
entity |
| Predicate | vocalSoloistType |
P46281
|
FINISHED |
| Object | soprano |
—
|
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: soprano | Statement: [Mahler Symphony No. 8, vocalSoloistType, soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalSoloistType Context triple: [Mahler Symphony No. 8, vocalSoloistType, soprano]
-
A.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
B.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
C.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
D.
isVocalShowcaseFor
Indicates that something serves as a performance or context specifically designed to highlight and display another entity’s vocal abilities.
-
E.
vocalRequirement
Indicates that a particular action, role, or participation involves a specified need or condition related to vocal use, such as speaking or singing.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651334c08190a9514faa36e7812d |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.