Triple
T21143422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Air Traffic Control Centre |
E520989
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air traffic control centre |
C3808
|
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 traffic control centre Context triple: [London Air Traffic Control Centre, instanceOf, air traffic control centre]
-
A.
air traffic control tower
A structure at an airport from which air traffic controllers monitor and direct aircraft movements on the ground and in the airspace around the airport to ensure safe and efficient operations.
-
B.
air navigation organization
chosen
An air navigation organization is an entity responsible for planning, managing, and controlling the safe and efficient movement of aircraft through designated airspace using air traffic services, communication, navigation, and surveillance systems.
-
C.
air traffic management systems manufacturer
A company that designs, develops, and produces integrated systems and technologies used to monitor, control, and optimize the safe and efficient movement of aircraft in airspace and at airports.
-
D.
command and control centre
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.
-
E.
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.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:57 p.m.