Triple
T31575562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-11A Battlefield Airborne Communications Node |
E805688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne communications relay platform |
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 communications relay platform Context triple: [E-11A Battlefield Airborne Communications Node, instanceOf, airborne communications relay platform]
-
A.
satellite platform derivative
A satellite platform derivative is a modified version of an existing satellite bus or platform, adapted with changes in structure, subsystems, or payload interfaces to meet new mission requirements while leveraging the original design.
-
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.
pilotless aircraft
A pilotless aircraft is an unmanned aerial vehicle that operates without an onboard human pilot, controlled either remotely or autonomously via onboard systems.
-
D.
airborne radar system
An airborne radar system is an integrated aircraft-mounted sensor suite that emits radio waves and processes their reflections to detect, track, and characterize objects or terrain in the surrounding air and ground environment.
-
E.
air-to-air refuelling aircraft
An air-to-air refuelling aircraft is a specialized military aircraft equipped to transfer fuel in flight to other aircraft, extending their range and mission endurance.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:21 p.m.