Triple
T18021007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinoatrial node |
E431115
|
entity |
| Predicate | stimulationEffectOf |
P53074
|
FINISHED |
| Object | sympathetic activation increases firing rate |
—
|
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: sympathetic activation increases firing rate | Statement: [Sinoatrial node, stimulationEffectOf, sympathetic activation increases firing rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stimulationEffectOf Context triple: [Sinoatrial node, stimulationEffectOf, sympathetic activation increases firing rate]
-
A.
providesSensoryEffects
Indicates that one entity causes or contributes to sensory experiences or perceptions in another entity.
-
B.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
measuredEffect
Indicates that an action or process has produced a specific, quantified outcome or impact on something.
-
D.
providesEffect
Indicates that one entity causes, delivers, or produces a particular effect or outcome on another entity.
-
E.
effectOfActivities
Indicates the causal impact that certain activities have on a particular outcome, state, or condition.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c1c5f88190a059ce4f86f7ed36 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.