Triple
T9807661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subtitle VI – Earth Observations |
E238192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subtitle of U.S. space law |
C26876
|
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: subtitle of U.S. space law Context triple: [Subtitle VI – Earth Observations, instanceOf, subtitle of U.S. space law]
-
A.
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.
-
B.
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.
-
C.
uncrewed spaceflight
Uncrewed spaceflight is the operation of spacecraft without human passengers onboard, using automated systems and remote control to conduct missions such as exploration, observation, and technology testing in space.
-
D.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
-
E.
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.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.