Triple
T31535496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nigrostriatal pathway |
E804590
|
entity |
| Predicate | involvesReceptor |
P149276
|
FINISHED |
| Object | dopamine D1 receptor |
—
|
NE NERFINISHED |
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: dopamine D1 receptor | Statement: [nigrostriatal pathway, involvesReceptor, dopamine D1 receptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesReceptor Context triple: [nigrostriatal pathway, involvesReceptor, dopamine D1 receptor]
-
A.
receptorTypeInteractedWith
Indicates that one entity has interacted with, bound to, or otherwise engaged a specific type of receptor.
-
B.
receptor
chosen
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
C.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
D.
receptorInput
Indicates that a receptor receives or is provided with an input signal or stimulus from another entity.
-
E.
targetsReceptor
Indicates that one entity is directed toward, binds to, or is designed to act upon a specific receptor.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 30, 2026, 10:03 p.m.