Triple
T8027804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League for Spiritual Discovery |
E186899
|
entity |
| Predicate | religiousUseOf |
P56479
|
FINISHED |
| Object | lysergic acid diethylamide |
—
|
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: lysergic acid diethylamide | Statement: [League for Spiritual Discovery, religiousUseOf, lysergic acid diethylamide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousUseOf Context triple: [League for Spiritual Discovery, religiousUseOf, lysergic acid diethylamide]
-
A.
usedReligionFor
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
B.
isUsedByReligion
chosen
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
-
C.
sacramentalUseOf
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
D.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
E.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.