Triple
T4824763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galen Black |
E107795
|
entity |
| Predicate | religiousPracticeInvolved |
P21643
|
FINISHED |
| Object | sacramental use of peyote |
—
|
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: sacramental use of peyote | Statement: [Galen Black, religiousPracticeInvolved, sacramental use of peyote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousPracticeInvolved Context triple: [Galen Black, religiousPracticeInvolved, sacramental use of peyote]
-
A.
practicesReligion
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
B.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
C.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
D.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
-
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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.