Triple
T27749359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAGE Direction Centers |
E702074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air defense command center |
C32431
|
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: air defense command center Context triple: [SAGE Direction Centers, instanceOf, air defense command center]
-
A.
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.
-
B.
command-and-control facility
A command-and-control facility is a secure, centralized location equipped with communication, monitoring, and decision-support systems used to direct and coordinate operations and resources in real time.
-
C.
command and control centre
chosen
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.
ground-based air defense system
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
-
E.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:18 p.m.