Triple
T26304160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | somatic marker hypothesis |
E661634
|
entity |
| Predicate | neuralBasis |
P160228
|
FINISHED |
| Object | amygdala |
—
|
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: amygdala | Statement: [somatic marker hypothesis, neuralBasis, amygdala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neuralBasis Context triple: [somatic marker hypothesis, neuralBasis, amygdala]
-
A.
neuralBasis
chosen
Indicates that one entity serves as the neural or brain-based mechanism underlying, enabling, or explaining the function, behavior, or property of another entity.
-
B.
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.
-
C.
hasNeuralNetwork
Indicates that an entity possesses, incorporates, or is equipped with a neural network.
-
D.
usesNeuralNetworks
Indicates that one entity employs neural network models or techniques as part of its functioning, processing, or decision-making.
-
E.
brainMass
Indicates the mass of an entity’s brain, typically measured as a physical quantity such as in grams or kilograms.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee22a908190a62640e48c2e7659 |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:17 p.m.