Triple
T14456197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priory of Sion |
E358464
|
entity |
| Predicate | hasThemeInFiction |
P76865
|
FINISHED |
| Object | religious conspiracy |
—
|
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: religious conspiracy | Statement: [Priory of Sion, hasThemeInFiction, religious conspiracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeInFiction Context triple: [Priory of Sion, hasThemeInFiction, religious conspiracy]
-
A.
fictionalTheme
Indicates that a work, element, or context is centered around or characterized by a fictional theme or motif.
-
B.
hasFeatureInFiction
Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
-
C.
hasThemeInStory
chosen
Indicates that a particular theme is present or plays a significant role within a given story.
-
D.
literaryThemeInvolvement
Indicates the involvement or presence of a particular literary theme within a work, passage, or character arc.
-
E.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.