Triple
T3833525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VX |
E91072
|
entity |
| Predicate | effectOnBody |
P40373
|
FINISHED |
| Object | accumulation of acetylcholine at synapses |
—
|
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: accumulation of acetylcholine at synapses | Statement: [VX, effectOnBody, accumulation of acetylcholine at synapses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnBody Context triple: [VX, effectOnBody, accumulation of acetylcholine at synapses]
-
A.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
B.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
C.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
D.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
E.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb88b8a8819082d4bdbc5bc45366 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.