Triple
T10004244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASAMS fire distribution center |
E198202
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | command and control node |
C13593
|
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: command and control node Context triple: [NASAMS fire distribution center, instanceOf, command and control node]
-
A.
command-and-control framework
A command-and-control framework is a structured system that enables centralized coordination, tasking, and monitoring of distributed agents or components, often used to manage operations, automation, or cyber activities.
-
B.
deployable air command and control centre
A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
-
C.
central control system
chosen
A central control system is a coordinating entity that monitors, manages, and directs the operations of interconnected components or subsystems to achieve overall system objectives.
-
D.
control plane component
A control plane component is a system element responsible for managing, configuring, and orchestrating the behavior and state of underlying data plane resources within a distributed or networked environment.
-
E.
network nodes
Network nodes are individual connection points within a communication system that can create, receive, or transmit data across the network.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 8:51 p.m.