Triple
T16621360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Air Support Squadron |
E403838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation command and control unit |
C26150
|
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: aviation command and control unit Context triple: [Marine Air Support Squadron, instanceOf, aviation command and control unit]
-
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.
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.
-
C.
aviation command billet
An aviation command billet is a designated leadership position within an aviation organization responsible for directing, managing, and overseeing the operations, personnel, and resources of an aviation unit or command.
-
D.
air control squadron
chosen
An air control squadron is a military unit responsible for providing radar surveillance, airspace management, and command and control of aircraft within a designated area of operations.
-
E.
airborne command post
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.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.