Triple
T12620300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Druidry |
E301359
|
entity |
| Predicate | mayIncludeBeliefIn |
P78381
|
FINISHED |
| Object | polytheism |
—
|
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: polytheism | Statement: [Druidry, mayIncludeBeliefIn, polytheism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeBeliefIn Context triple: [Druidry, mayIncludeBeliefIn, polytheism]
-
A.
requiresBeliefIn
Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
-
B.
invokesBeliefIn
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
C.
allowsBeliefSystem
chosen
Indicates that one entity permits, supports, or enables the existence, practice, or adoption of a particular belief system by another entity.
-
D.
mayEntail
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
-
E.
hasVariantBelief
Indicates that one entity holds a belief that is an alternative or differing version of another entity’s belief.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.