Triple
T36131045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell L. Schweickart |
E1045015
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space safety advocate |
C65400
|
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 safety advocate Context triple: [Russell L. Schweickart, instanceOf, space safety advocate]
-
A.
spaceflight safety initiative
A spaceflight safety initiative is a coordinated program of policies, technologies, and procedures designed to prevent accidents, protect crew and payloads, and ensure the safe operation of spacecraft throughout all mission phases.
-
B.
space exploration advocate
A space exploration advocate is an individual who actively promotes the scientific, economic, and societal benefits of exploring outer space and supports policies and initiatives that advance space missions and technologies.
-
C.
space advocacy organization
A space advocacy organization is a group dedicated to promoting the exploration, development, and peaceful use of outer space through public outreach, policy influence, and support for space-related research and industry.
-
D.
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.
-
E.
spaceflight pioneer
A spaceflight pioneer is an individual or organization that significantly advances the development, technology, or exploration of space, often by achieving groundbreaking missions or innovations.
- F. None of above. chosen
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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.