Triple
T23352533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACAMO |
E592954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne command and control mission |
C18649
|
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: airborne command and control mission Context triple: [TACAMO, instanceOf, airborne command and control mission]
-
A.
military aviation command
A military aviation command is an organizational unit responsible for planning, directing, coordinating, and controlling the employment, readiness, and support of air forces to achieve strategic and operational military objectives.
-
B.
airborne command post
chosen
An airborne command post is an aircraft equipped with advanced communications, surveillance, and control systems that enables military or government leaders to direct operations and maintain command and control while in flight.
-
C.
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.
-
D.
combat aircraft mission system suite
A combat aircraft mission system suite is an integrated collection of avionics, sensors, communication, navigation, and weapon management subsystems that work together to plan, execute, and support military air missions.
-
E.
command and control activity
A command and control activity is an operation or process through which authority is exercised to direct, coordinate, and manage resources and actions toward achieving specific objectives.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:20 p.m.