Triple
T32327231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dream of Gerontius |
E825945
|
entity |
| Predicate | principalSoloVoice |
P9645
|
FINISHED |
| Object | tenor (Gerontius) |
—
|
NE NERFINISHED |
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: tenor (Gerontius) | Statement: [The Dream of Gerontius, principalSoloVoice, tenor (Gerontius)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalSoloVoice Context triple: [The Dream of Gerontius, principalSoloVoice, tenor (Gerontius)]
-
A.
vocalSoloists
Indicates that one or more entities perform as solo vocalists in a musical work or performance.
-
B.
primaryInstrumentalVoice
Indicates that one entity serves as the main instrumental or musical voice through which another entity is expressed, performed, or realized.
-
C.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
D.
soloistRole
Indicates that an entity has the role of performing as a soloist within a work, event, or performance.
-
E.
primaryVocalist
chosen
Indicates that the subject is the main singer or lead vocal performer for the object (such as a song, track, or musical work).
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bde8913c8190b620cc572b19a3ed |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:47 a.m.