Triple
T26815938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GABA |
E675120
|
entity |
| Predicate | isReleasedInResponseTo |
P163072
|
FINISHED |
| Object | nerve impulse |
—
|
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: nerve impulse | Statement: [GABA, isReleasedInResponseTo, nerve impulse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReleasedInResponseTo Context triple: [GABA, isReleasedInResponseTo, nerve impulse]
-
A.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
B.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
C.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
D.
someReleasedTo
Indicates that at least one instance of an item or entity has been released or made available to a specified recipient or target.
-
E.
commissionedInResponseTo
Indicates that something was formally requested or initiated as a direct reaction to a specific prior event, work, or circumstance.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:52 a.m.