Triple
T27540029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSTC-A |
E695209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S.-led security assistance command |
C52897
|
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: U.S.-led security assistance command Context triple: [CSTC-A, instanceOf, U.S.-led security assistance command]
-
A.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
B.
Geographic combatant command
A geographic combatant command is a unified military command responsible for planning and conducting operations within a specific, defined region of the world.
-
C.
Air and Space Operations Center
An Air and Space Operations Center is a command and control facility that plans, directs, coordinates, and monitors air and space operations to achieve assigned military objectives.
-
D.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
E.
United States Army service component command
A United States Army service component command is the Army organization assigned to support, integrate, and provide Army forces to a specific unified combatant command, serving as its primary Army headquarters for planning and operations.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:30 p.m.