Triple
T2523499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBD |
E55577
|
entity |
| Predicate | mayInteractWith |
P3970
|
FINISHED |
| Object | CYP450-metabolized drugs |
—
|
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: CYP450-metabolized drugs | Statement: [CBD, mayInteractWith, CYP450-metabolized drugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayInteractWith Context triple: [CBD, mayInteractWith, CYP450-metabolized drugs]
-
A.
mayEngageIn
Indicates that one entity is permitted or authorized to participate in or perform a particular activity or interaction with another entity.
-
B.
mayEnter
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
C.
mayConduct
Indicates that one entity is permitted or authorized to carry out, perform, or execute a particular action, process, or operation on or with another entity.
-
D.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
E.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.