Triple
T10610195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | endocannabinoid system |
E275984
|
entity |
| Predicate | ligandOf |
P37016
|
FINISHED |
| Object | CB1 receptor |
—
|
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: CB1 receptor | Statement: [endocannabinoid system, ligandOf, CB1 receptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ligandOf Context triple: [endocannabinoid system, ligandOf, CB1 receptor]
-
A.
hasProteinBinding
Indicates that one entity is capable of physically binding to or interacting specifically with a protein.
-
B.
substrateAffinity
Indicates the degree to which one entity tends to bind to, interact with, or preferentially act upon a particular substrate.
-
C.
isProdrugOf
Indicates that one substance is a precursor form that is metabolized in the body to produce the active form of another substance.
-
D.
hasMolecularTarget
chosen
Indicates that one entity (such as a drug or compound) is directed toward, binds to, or specifically interacts with a particular molecular target (such as a protein, receptor, or gene).
-
E.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:32 p.m.