Triple
T823398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Operations Command |
E17799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Space Force field command |
C6111
|
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: United States Space Force field command Context triple: [Space Operations Command, instanceOf, United States Space Force field command]
-
A.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
B.
United States Air Force base
A United States Air Force base is a military installation that supports Air Force operations through facilities for aircraft, personnel, training, logistics, and command and control activities.
-
C.
reserve component of the United States Air Force
The reserve component of the United States Air Force is the part-time military force composed of Air Force Reserve and Air National Guard units that support and augment the active-duty Air Force during peacetime and wartime operations.
-
D.
United States Army installation
A United States Army installation is a designated military facility, base, or post that supports the housing, training, operations, logistics, and administration of Army personnel and equipment.
-
E.
United States Army major command
A United States Army major command is a high-level organizational entity responsible for overseeing and directing large-scale Army operations, resources, and support functions within a specific mission area or geographic region.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.