Triple
T25387819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sun, Whose Rays Are All Ablaze |
E631571
|
entity |
| Predicate | associatedCharacterVoiceType |
P187769
|
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: [The Sun, Whose Rays Are All Ablaze, associatedCharacterVoiceType, soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCharacterVoiceType Context triple: [The Sun, Whose Rays Are All Ablaze, associatedCharacterVoiceType, soprano]
-
A.
sungByCharacterVoiceType
chosen
Indicates that a song or vocal part is performed by a character with a specified voice type (e.g., soprano, tenor, bass).
-
B.
characterTypeVoiced
Indicates that one character serves as the voice actor or vocal performer for another character.
-
C.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
D.
voiceCharacter
Indicates that one entity provides the voice for, or vocally portrays, a particular character in a work.
-
E.
hasVoiceActing
Indicates that one entity provides voice performance for a character, role, or work associated with another entity.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 21, 2026, 1:47 p.m.