Triple
T27920944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSD Church |
E706200
|
entity |
| Predicate | treatsAsSacrament |
P7392
|
FINISHED |
| Object | LSD |
—
|
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: LSD | Statement: [LSD Church, treatsAsSacrament, LSD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsAsSacrament Context triple: [LSD Church, treatsAsSacrament, LSD]
-
A.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
-
B.
confersSacrament
Indicates that one entity formally administers or bestows a religious sacrament upon another entity.
-
C.
sacramentalUseOf
chosen
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
D.
sacramentalSign
Indicates that one entity functions as a visible, ritual sign that conveys or symbolizes a sacred or divine reality in relation to another entity.
-
E.
formOfSacrament
Indicates that one entity is a specific liturgical or ritual form in which a sacrament is administered or expressed.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 6:57 p.m.