Triple
T20694652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health Committee (OECD) |
E508633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health policy coordination body |
C21514
|
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: health policy coordination body Context triple: [Health Committee (OECD), instanceOf, health policy coordination body]
-
A.
science policy coordination body
A science policy coordination body is an organization that aligns scientific research, evidence, and expertise with policymaking processes across institutions and sectors to ensure coherent, informed, and effective public policy.
-
B.
health policy department
A health policy department is an organizational unit responsible for researching, developing, analyzing, and advising on policies that shape healthcare systems, public health initiatives, and regulatory frameworks.
-
C.
intergovernmental coordination agency
chosen
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
-
D.
intelligence coordination body
An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security objectives.
-
E.
health agency
A health agency is an organization responsible for planning, coordinating, and delivering public health services, policies, and programs to protect and improve the health of a population.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:10 p.m.