Triple
T10873005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayahuasca |
E256704
|
entity |
| Predicate | associatedWithExperience |
P22109
|
FINISHED |
| Object | visions |
—
|
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: visions | Statement: [Ayahuasca, associatedWithExperience, visions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithExperience Context triple: [Ayahuasca, associatedWithExperience, visions]
-
A.
recommendedExperience
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
-
B.
comparesExperienceTo
Indicates that one entity evaluates or contrasts the level, amount, or quality of experience of one entity with that of another.
-
C.
experienceType
chosen
Indicates the specific kind or category of experience associated with an entity or event.
-
D.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
E.
basedOnExperience
Indicates that something is determined, chosen, or formed according to prior experience or experiential knowledge.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751885b348190baf6eb606089a438 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.