Triple
T22628033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Doctrine Publication 3-14 |
E558476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space operations doctrine |
C19681
|
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 operations doctrine Context triple: [Army Doctrine Publication 3-14, instanceOf, space operations doctrine]
-
A.
space operations
chosen
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.
-
B.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
-
C.
space operations training unit
A space operations training unit is an organizational entity responsible for preparing personnel to plan, execute, and support space missions through specialized education, simulation, and hands-on operational training.
-
D.
space operations center
A space operations center is a specialized facility that monitors, controls, and coordinates spacecraft, satellites, and related space missions in real time.
-
E.
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.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:02 p.m.