Triple
T23598524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neuron doctrine |
E582684
|
entity |
| Predicate | acknowledgesException |
P152871
|
FINISHED |
| Object | electrical coupling via gap junctions |
—
|
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: electrical coupling via gap junctions | Statement: [neuron doctrine, acknowledgesException, electrical coupling via gap junctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acknowledgesException Context triple: [neuron doctrine, acknowledgesException, electrical coupling via gap junctions]
-
A.
supportsExceptionProcessing
Indicates that one entity provides the capability or mechanism for another entity to handle or process exceptions.
-
B.
initiallyFailsToAcknowledge
Indicates that one entity does not recognize, admit, or respond to another entity or situation at the beginning of an interaction or process.
-
C.
notableException
Indicates that something or someone stands out as an unusual or noteworthy deviation from an expected pattern, rule, or general case.
-
D.
throwsException
Indicates that an operation or method results in an exception being raised during its execution.
-
E.
hasExceptionFor
Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b091992c819085f8aa6cb91cb76a |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:43 p.m.