Triple
T30087011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | medial geniculate nucleus |
E764626
|
entity |
| Predicate | receivesInhibitoryInput |
P173410
|
FINISHED |
| Object | GABAergic neurons |
—
|
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: GABAergic neurons | Statement: [medial geniculate nucleus, receivesInhibitoryInput, GABAergic neurons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesInhibitoryInput Context triple: [medial geniculate nucleus, receivesInhibitoryInput, GABAergic neurons]
-
A.
receptorInput
Indicates that a receptor receives or is provided with an input signal or stimulus from another entity.
-
B.
inhibits
Indicates that one entity prevents, restrains, or reduces the activity, effect, or occurrence of another entity.
-
C.
synapsesAt
Indicates that one neural element forms a synaptic connection at, or onto, another specified location or structure.
-
D.
inhibitionUse
Indicates that one entity uses or applies an inhibitory effect to reduce, block, or suppress the activity or function of another entity.
-
E.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
- F. None of above. chosen
Provenance (4 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 29, 2026, 7:04 p.m.