Triple
T442797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannabis |
E10150
|
entity |
| Predicate | producesCompound |
P490
|
FINISHED |
| Object | tetrahydrocannabinol |
—
|
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: tetrahydrocannabinol | Statement: [Cannabis, producesCompound, tetrahydrocannabinol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesCompound Context triple: [Cannabis, producesCompound, tetrahydrocannabinol]
-
A.
produces
chosen
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
B.
specialComposition
Indicates that one entity is composed of another in a distinctive or non-standard way, highlighting a particular or exceptional form of composition between them.
-
C.
isCompilationOf
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
D.
compositionChamber
Indicates a relationship where a chamber or enclosed space is used as the setting or environment in which a composition (such as a musical, chemical, or artistic work) is created or formed.
-
E.
formulatedIn
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef43e8f88190a5d368add11a38c0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2edde2b9c8190bd20b582eb4c5065 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.