Triple
T18088123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sympathetic nervous system |
E432891
|
entity |
| Predicate | innervates |
P129456
|
FINISHED |
| Object | heart |
—
|
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: heart | Statement: [Sympathetic nervous system, innervates, heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innervates Context triple: [Sympathetic nervous system, innervates, heart]
-
A.
innervatedBy
Indicates that a structure receives nerve supply or stimulation from the specified neural source.
-
B.
innervation
chosen
Indicates that one entity (typically a nerve or neuron) supplies nerve fibers to another entity, enabling neural control or communication.
-
C.
vagusNerveInnervates
Indicates that the vagus nerve provides nerve supply to, and functionally controls or influences, a target structure.
-
D.
sacralOutflowInnervates
Indicates that neural fibers emerging from the sacral region of the spinal cord provide innervation to a target structure.
-
E.
neuralInterface
Indicates a direct connection or communication link established between a neural system (biological or artificial) and another device or system for transmitting signals or information.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd16234c8190b547e893a829d6c5 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.