Triple
T111699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native American Church |
E2261
|
entity |
| Predicate | regardedPeyoteAs |
P1120
|
FINISHED |
| Object | sacred medicine |
—
|
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: sacred medicine | Statement: [Native American Church, regardedPeyoteAs, sacred medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regardedPeyoteAs Context triple: [Native American Church, regardedPeyoteAs, sacred medicine]
-
A.
considered
chosen
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
-
B.
isConsideredByAdherents
Indicates that something (such as a belief, practice, object, or figure) is regarded or held in a particular way by the people who adhere to a specific faith, ideology, or group.
-
C.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
D.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.