Triple

T15866887
Position Surface form Disambiguated ID Type / Status
Subject Air Transport Wing Aalborg E384736 entity
Predicate instanceOf P0 FINISHED
Object Royal Danish Air Force unit C36573 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: Royal Danish Air Force unit
Context triple: [Air Transport Wing Aalborg, instanceOf, Royal Danish Air Force unit]
  • A. Belgian Air Force unit
    A Belgian Air Force unit is an organizational entity within the Belgian Air Component responsible for executing specific air defense, support, training, or operational missions using assigned personnel, aircraft, and equipment.
  • B. Belgian Air Force unit
    A Belgian Air Force unit is an organizational subdivision of the Belgian Air Component, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions within national and allied defense frameworks.
  • C. Royal Australian Air Force unit
    A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
  • D. German military aviation unit
    A German military aviation unit is an organized formation within Germany’s armed forces that operates, maintains, and supports aircraft to conduct air missions for defense, reconnaissance, transport, and combat operations.
  • E. Polish Air Force unit
    A Polish Air Force unit is an organizational entity within Poland’s air arm responsible for operating, maintaining, and supporting assigned aircraft and air defense systems to fulfill national defense and allied mission objectives.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
Created at: April 10, 2026, 4:50 a.m.