Triple
T13521283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri Michaux |
E322900
|
entity |
| Predicate | usedSubstanceInWork |
P10343
|
FINISHED |
| Object | mescaline |
—
|
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: mescaline | Statement: [Henri Michaux, usedSubstanceInWork, mescaline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSubstanceInWork Context triple: [Henri Michaux, usedSubstanceInWork, mescaline]
-
A.
usedSubstance
Indicates that an entity has consumed, applied, or otherwise made use of a particular substance.
-
B.
usedInWork
chosen
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
C.
associatedWithSubstance
Indicates that one entity has a relevant connection or involvement with a particular substance, such as use, presence, exposure, or composition.
-
D.
acceptsSubstance
Indicates that an entity receives, takes in, or allows the use of a specified substance.
-
E.
hasAddictiveSubstance
Indicates that an entity contains or involves a substance capable of causing addiction in those who use or consume it.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa3df0c8190804174695587f0ea |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:44 p.m.