Triple
T32742120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithVocalForces |
P135747
|
FINISHED |
| Object | soprano solo |
—
|
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 solo | Statement: [Resurrection, associatedWithVocalForces, soprano solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithVocalForces Context triple: [Resurrection, associatedWithVocalForces, soprano solo]
-
A.
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.
-
B.
hasVocalForces
Indicates that an entity involves or employs vocal performers or vocal parts as a contributing force.
-
C.
vocalComponent
Indicates that one entity functions as a vocal or sung component within, or contributing to, another entity (such as a work, performance, or recording).
-
D.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
-
E.
vocalCounterpartType
Indicates the type or category of a vocal counterpart relationship that one entity has to another (e.g., spoken, sung, dubbed, narrated).
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.