Triple
T31729083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude to Parsifal |
E809805
|
entity |
| Predicate | setsAtmosphereFor |
P47237
|
FINISHED |
| Object | Parsifal |
—
|
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: Parsifal | Statement: [Prelude to Parsifal, setsAtmosphereFor, Parsifal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsAtmosphereFor Context triple: [Prelude to Parsifal, setsAtmosphereFor, Parsifal]
-
A.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
B.
hasAtmosphericArrangement
Indicates that one entity possesses or exhibits a particular configuration or structure of atmospheric components or layers in relation to another entity or defined standard.
-
C.
atmosphereStyle
Indicates the general mood, ambiance, or experiential character associated with a place, event, or environment.
-
D.
usesAtmosphereOf
Indicates that one entity makes use of or operates within the atmospheric conditions or composition associated with another entity.
-
E.
capturesAtmosphereOf
chosen
Indicates that one entity successfully conveys or reflects the overall mood, tone, or ambiance characteristic of 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab1d46a4819098cbd250564c7d85 |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:21 p.m.