Triple
T22098658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Space Force bases |
E546107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space force installation |
C1086
|
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 force installation Context triple: [United States Space Force bases, instanceOf, space force installation]
-
A.
United States Space Force organizational system
The United States Space Force organizational system is the structured arrangement of commands, field units, roles, and processes designed to plan, conduct, and support space operations in alignment with national defense objectives.
-
B.
United States Space Force field command
A United States Space Force field command is a major organizational echelon responsible for executing a broad, mission-specific portfolio of space operations, support, or training functions under the direction of Space Operations Command.
-
C.
military installation
chosen
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
D.
United States Space Force delta
A United States Space Force delta is a military organizational unit, roughly equivalent to a wing, that is responsible for a specific mission area such as operations, training, or support within the Space Force.
-
E.
space launch facility
A space launch facility is a specialized complex equipped with infrastructure, systems, and support services for preparing, launching, and sometimes recovering spacecraft and launch vehicles.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:30 p.m.