Triple
T31728771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurnemanz |
E809798
|
entity |
| Predicate | explainsToCharacter |
P141803
|
FINISHED |
| Object | Amfortas’s suffering |
—
|
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: Amfortas’s suffering | Statement: [Gurnemanz, explainsToCharacter, Amfortas’s suffering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsToCharacter Context triple: [Gurnemanz, explainsToCharacter, Amfortas’s suffering]
-
A.
explainedByCharacter
chosen
Indicates that something (such as an event, situation, or piece of information) is explained or clarified by a particular character.
-
B.
explainsToAudience
Indicates that one entity provides an explanation or clarification to an audience as the intended recipients.
-
C.
clarifiesThat
Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
-
D.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
E.
spokenToCharacter
Indicates that one character has verbally addressed or communicated directly with another character.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:20 p.m.