Triple
T4131750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHO IHR contact points |
E85056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international health communication mechanism |
C2063
|
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: international health communication mechanism Context triple: [WHO IHR contact points, instanceOf, international health communication mechanism]
-
A.
international cooperation mechanism
chosen
An international cooperation mechanism is a structured framework, agreement, or institution through which multiple countries coordinate policies, share resources, and jointly address cross-border issues or common goals.
-
B.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
-
C.
international legal mechanism
An international legal mechanism is a formal process, institution, or instrument established by states or international organizations to create, interpret, enforce, or resolve disputes about obligations under international law.
-
D.
international office
An international office is an organizational unit that manages and supports an institution’s global activities, partnerships, and services for international stakeholders.
-
E.
international framework
An international framework is a structured set of principles, rules, and mechanisms agreed upon by multiple countries to guide cooperation, coordination, and decision-making on shared global issues.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:42 p.m.