Triple
T20611919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMiK |
E506467
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international organization mission |
C16314
|
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 organization mission Context triple: [OMiK, instanceOf, international organization mission]
-
A.
international mission
An international mission is a coordinated effort by multiple countries or global organizations to achieve a shared objective—such as humanitarian aid, peacekeeping, scientific research, or development—across national borders.
-
B.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
international organization component
chosen
An international organization component is a structural unit or subdivision within an international organization that carries out specific functions, responsibilities, or services in support of the organization’s overall mission and objectives.
-
E.
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.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:41 a.m.