Triple
T18924068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global immunization partners |
E462932
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-stakeholder initiative |
C999
|
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: multi-stakeholder initiative Context triple: [Global immunization partners, instanceOf, multi-stakeholder initiative]
-
A.
multistakeholder organization
chosen
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
B.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
C.
international initiative
An international initiative is a coordinated effort among multiple countries or global organizations aimed at addressing shared challenges or achieving common goals across national borders.
-
D.
global initiative
A global initiative is a coordinated, large-scale effort involving multiple countries or international organizations aimed at addressing worldwide challenges or achieving shared global objectives.
-
E.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.