Triple
T17541804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACAN |
E427216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical air navigation system |
C28613
|
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: tactical air navigation system Context triple: [TACAN, instanceOf, tactical air navigation system]
-
A.
air navigation organization
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.
aviation coding system
An aviation coding system is a structured set of standardized codes and rules used to represent, transmit, and interpret aviation-related information such as airports, routes, aircraft, and procedures in a consistent, machine-readable form.
-
C.
terrestrial navigation system
chosen
A terrestrial navigation system is a ground-based infrastructure and associated equipment that determine a vehicle’s position, velocity, and course using signals or references located on or near the Earth’s surface.
-
D.
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.
-
E.
satellite-based augmentation system
A satellite-based augmentation system is an overlay to global navigation satellite systems that uses additional satellites and ground stations to provide improved accuracy, integrity, and availability for positioning and navigation services.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.