Triple
T21817014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–Japan space cooperation |
E538629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international space cooperation framework |
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 space cooperation framework Context triple: [EU–Japan space cooperation, instanceOf, international space cooperation framework]
-
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 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.
-
C.
space law instrument
A space law instrument is a formal legal document—such as a treaty, agreement, or regulation—that establishes rules and principles governing activities and relationships in outer space and related celestial environments.
-
D.
space law treaty
A space law treaty is a formal international agreement that establishes legal principles, rights, and obligations governing the exploration, use, and activities in outer space among states and other authorized entities.
-
E.
spaceflight program partnership
A spaceflight program partnership is a collaborative arrangement between organizations, agencies, or nations to jointly plan, fund, develop, and operate missions and infrastructure for space exploration or utilization.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:54 p.m.