Triple
T10517588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal Radar Approach Control |
E248073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radar approach control facility |
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: radar approach control facility Context triple: [Terminal Radar Approach Control, instanceOf, radar approach control facility]
-
A.
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.
-
B.
instrumentation radar
Instrumentation radar is a specialized radar system used to track, measure, and record the performance and trajectory of test objects such as missiles, aircraft, or spacecraft during experimental or evaluation activities.
-
C.
radar subsystem
A radar subsystem is a component of a larger system that generates, transmits, receives, and processes radio-frequency signals to detect, locate, and track objects in its environment.
-
D.
race control tower
A race control tower is a centralized facility at a racing venue from which officials monitor the event, manage timing and scoring, enforce rules, and coordinate safety and communication.
-
E.
radar system family
A radar system family is a group of related radar systems that share a common architecture, technology base, and design principles while differing in specific capabilities, configurations, or applications.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:28 p.m.