Triple
T35121943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia Pacific Heart Rhythm Society |
E1014186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional heart rhythm society |
C6926
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regional heart rhythm society Context triple: [Asia Pacific Heart Rhythm Society, instanceOf, regional heart rhythm society]
-
A.
subsidiary association of the European Society of Cardiology
A subsidiary association of the European Society of Cardiology is an affiliated organizational unit that operates under the ESC’s umbrella to advance specific cardiovascular disciplines, professional groups, or regional interests in alignment with the Society’s overall mission.
-
B.
cardiovascular institute
A cardiovascular institute is a specialized medical center dedicated to the prevention, diagnosis, treatment, and research of heart and blood vessel diseases.
-
C.
American Heart Association program
An American Heart Association program is an organized initiative designed to advance cardiovascular health through education, research support, advocacy, and community-based prevention and treatment efforts.
-
D.
regional chapter network
chosen
A regional chapter network is a coordinated system of local chapters within a defined geographic area that collaborate under a shared mission, governance structure, and resource framework to advance common goals.
-
E.
cardiology journal
A cardiology journal is a periodical publication that presents peer-reviewed research, reviews, and clinical insights focused on the cardiovascular system and heart-related diseases.
- F. None of above.
Provenance (1 batch)
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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.