Triple
T35132149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siona |
E1014464
|
entity |
| Predicate | ceremonialUseOf |
P6169
|
FINISHED |
| Object | psychoactive plants |
—
|
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: psychoactive plants | Statement: [Siona, ceremonialUseOf, psychoactive plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialUseOf Context triple: [Siona, ceremonialUseOf, psychoactive plants]
-
A.
ceremonialUse
chosen
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
B.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
C.
ceremonialFeatures
Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
-
D.
ceremonialIssue
Indicates a formal act of presenting or conferring something (such as a document, item, or status) in a ceremonial or ritualized context.
-
E.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c6a861881909f0f3de4e935bd0e |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.