Triple
T3064093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis Accords |
E62062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space policy instrument |
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 instrument Context triple: [Artemis Accords, instanceOf, space policy instrument]
-
A.
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.
-
B.
space-grant institution
A space-grant institution is a college or university designated under the U.S. National Space Grant College and Fellowship Program to promote education, research, and public outreach in space-related fields.
-
C.
space agency
A space agency is an organization, typically government-funded, responsible for planning, developing, and conducting space missions, research, and related technologies.
-
D.
science and technology policy instrument
A science and technology policy instrument is a deliberate governmental or institutional tool—such as funding programs, regulations, tax incentives, or public–private partnerships—used to influence the direction, pace, and societal impact of scientific research and technological innovation.
-
E.
space mission
A space mission is a planned and coordinated endeavor to send spacecraft, instruments, or humans beyond Earth's atmosphere to achieve specific scientific, exploratory, commercial, or technological objectives.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:02 p.m.