Triple
T31535210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | locus coeruleus |
E804585
|
entity |
| Predicate | hasNeurotransmitter |
P169711
|
FINISHED |
| Object | norepinephrine |
—
|
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: norepinephrine | Statement: [locus coeruleus, hasNeurotransmitter, norepinephrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeurotransmitter Context triple: [locus coeruleus, hasNeurotransmitter, norepinephrine]
-
A.
neurotransmitter
Indicates that one entity functions as a chemical messenger released by a neuron to transmit signals to another cell across a synapse.
-
B.
neurotransmitterSystems
chosen
Indicates the relationship between an entity and the neurotransmitter pathways or systems it involves, affects, or is associated with in neural signaling.
-
C.
isPrimaryInhibitoryNeurotransmitterIn
Indicates that one neurotransmitter serves as the main inhibitory signaling chemical within a specified nervous system, region, or organism.
-
D.
hasBrainCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to the brain.
-
E.
hasNervousSystem
Indicates that an entity possesses a nervous system as a biological feature.
- 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_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: April 30, 2026, 10:03 p.m.