Triple
T21671209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligence and Operations Coordinating Centers |
E534847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional command hub |
C1953
|
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: regional command hub Context triple: [Intelligence and Operations Coordinating Centers, instanceOf, regional command hub]
-
A.
regional land command
A regional land command is a military organizational structure responsible for planning, directing, and coordinating all land-based operations and forces within a defined geographic area.
-
B.
regional center
chosen
A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
-
C.
command and control centre
A command and control centre is a centralized facility where information is collected, analyzed, and used to coordinate and direct operations, resources, and decision-making in real time.
-
D.
regional facilities engineering command
A regional facilities engineering command is an organizational unit responsible for planning, constructing, operating, and maintaining infrastructure and facilities within a defined geographic area to support mission and operational needs.
-
E.
regional air command
A regional air command is a military organizational unit responsible for planning, directing, and controlling air operations within a specific geographic area.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:37 p.m.