Triple
T30303285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarastro |
E770706
|
entity |
| Predicate | requiresFromProtagonists |
P196078
|
FINISHED |
| Object | trials of silence |
—
|
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: trials of silence | Statement: [Sarastro, requiresFromProtagonists, trials of silence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresFromProtagonists Context triple: [Sarastro, requiresFromProtagonists, trials of silence]
-
A.
protagonistMust
Indicates that a particular entity is required to serve as the main character or central focus within a narrative or scenario.
-
B.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
-
D.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
- F. None of above. chosen
Provenance (4 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 29, 2026, 7:49 p.m.