Triple
T1229216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan American Sanitary Conference |
E26397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional health governance mechanism |
C562
|
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 health governance mechanism Context triple: [Pan American Sanitary Conference, instanceOf, regional health governance mechanism]
-
A.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
B.
regional forum
chosen
A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
-
C.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
D.
public health partnership
A public health partnership is a collaborative alliance among governmental agencies, community organizations, healthcare providers, and other stakeholders that coordinates resources and efforts to improve population health outcomes and address public health challenges.
-
E.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.