Triple
T37105419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian space authorities (post-Soviet period) |
E918826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governmental space agency system |
C1669
|
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: governmental space agency system Context triple: [Ukrainian space authorities (post-Soviet period), instanceOf, governmental space agency system]
-
A.
space agency
chosen
A space agency is an organization, typically government-funded, responsible for planning, developing, and conducting space missions, research, and related technologies.
-
B.
space agency oversight body
A space agency oversight body is an authoritative organization responsible for monitoring, evaluating, and guiding a space agency’s policies, programs, safety, and compliance to ensure accountability, effectiveness, and alignment with national or international objectives.
-
C.
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.
-
D.
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.
-
E.
mission agency
A mission agency is an organization that recruits, equips, sends, and supports missionaries or mission teams to carry out religious, humanitarian, or development work across different regions or cultures.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.