Triple
T9169254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO International Geoscience Programme |
E220041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international research initiative |
C3131
|
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 research initiative Context triple: [UNESCO International Geoscience Programme, instanceOf, international research initiative]
-
A.
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.
-
B.
research initiative
A research initiative is a coordinated, goal-driven effort to investigate specific questions or problems, typically organized around a defined scope, methodology, timeline, and set of expected outcomes.
-
C.
international scientific programme
chosen
An international scientific programme is a coordinated, long-term research initiative involving multiple countries and institutions that collaboratively address shared scientific questions or global challenges.
-
D.
international programme
An international programme is a coordinated set of activities, courses, or initiatives designed and delivered across multiple countries or cultures to achieve shared educational, developmental, or strategic objectives.
-
E.
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.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:22 p.m.