Triple
T26276525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Plan on Space Policy of Japan |
E660586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space policy framework |
C11466
|
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: space policy framework Context triple: [Basic Plan on Space Policy of Japan, instanceOf, space policy framework]
-
A.
space policy body
A space policy body is an organization or governmental entity responsible for developing, coordinating, and overseeing laws, regulations, and strategic guidelines governing the exploration and use of outer space.
-
B.
space policy speech
A space policy speech is a formal address that outlines a government’s or organization’s strategic goals, priorities, and regulatory approaches for the exploration, utilization, and governance of outer space.
-
C.
space policy scholar
A space policy scholar is an expert who studies and analyzes the laws, regulations, governance frameworks, and political dynamics that shape national and international activities in outer space.
-
D.
space law instrument
chosen
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.
-
E.
space access mission area
The space access mission area encompasses the systems, operations, and infrastructure required to reliably and affordably deliver payloads and humans from Earth to space and between orbital or celestial destinations.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 9:56 p.m.