Triple
T11475624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Magic Flute |
E272017
|
entity |
| Predicate | containsMasonicAllusions |
P75542
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Magic Flute, containsMasonicAllusions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMasonicAllusions Context triple: [The Magic Flute, containsMasonicAllusions, yes]
-
A.
hasMasonicContext
chosen
Indicates that something is related to, influenced by, or situated within the traditions, symbolism, practices, or institutions of Freemasonry.
-
B.
hasMasonicBodyType
Indicates that an entity is associated with, or classified according to, a specific type or category of Masonic body.
-
C.
hasMysteryCult
Indicates that an entity is associated with, participates in, or possesses a mystery cult, typically involving secret or esoteric religious practices.
-
D.
hasAllegoricalDepictionsBy
Indicates that one entity is represented through allegorical depictions created by another entity.
-
E.
hasAllegoricalFigures
Indicates that a work, scene, or element includes figures that symbolically represent abstract ideas, concepts, or moral qualities.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.