Triple
T18020769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Right ventricle |
E431110
|
entity |
| Predicate | receivesImpulseVia |
P39632
|
FINISHED |
| Object | atrioventricular bundle |
—
|
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: atrioventricular bundle | Statement: [Right ventricle, receivesImpulseVia, atrioventricular bundle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesImpulseVia Context triple: [Right ventricle, receivesImpulseVia, atrioventricular bundle]
-
A.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
receptorSystem
chosen
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
C.
receiverAction
Indicates that the receiver of something performs or is associated with a specific action in the context of that transfer or interaction.
-
D.
receivesLivingFrom
Indicates that one entity obtains or is given a living organism or life-sustaining resource from another entity.
-
E.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
- 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.