Triple
T2132377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Traffic Control Centre |
E46569
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belgian Air Force unit |
C9857
|
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: Belgian Air Force unit Context triple: [Air Traffic Control Centre, instanceOf, Belgian Air Force unit]
-
A.
component of the French Air and Space Force
A component of the French Air and Space Force is an organizational subdivision, such as a command, unit, or formation, that performs specific operational, support, or administrative functions within France’s air and space defense structure.
-
B.
Luftwaffe wing
A Luftwaffe wing is a major operational air unit of the German Air Force, typically composed of several squadrons or groups equipped and organized to perform specific missions such as air defense, strike, or reconnaissance.
-
C.
fighter squadron
A fighter squadron is a military aviation unit composed of multiple fighter aircraft and their personnel, organized to conduct air-to-air and air-to-ground combat missions under a unified command.
-
D.
Royal Air Force squadron
A Royal Air Force squadron is a military aviation unit comprising aircraft, aircrew, and support personnel organized under a specific command structure to perform designated operational, training, or support roles.
-
E.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
- F. None of above. chosen
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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:44 p.m.