Triple

T15489724
Position Surface form Disambiguated ID Type / Status
Subject Kampfstaffel Metz E377147 entity
Predicate instanceOf P0 FINISHED
Object World War I air unit C35526 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: World War I air unit
Context triple: [Kampfstaffel Metz, instanceOf, World War I air unit]
  • A. World War I air operations
    World War I air operations encompass the use of aircraft for reconnaissance, air combat, bombing, and support missions that transformed military strategy and technology in the early 20th century.
  • B. World War I bomber
    A World War I bomber is a military aircraft designed and used during the First World War to carry and drop bombs on enemy targets, including strategic infrastructure, troop concentrations, and supply lines.
  • C. Royal Flying Corps squadron
    A Royal Flying Corps squadron is a military aviation unit of the British Army’s pre-1918 air arm, typically composed of multiple aircraft, aircrew, and ground personnel organized for reconnaissance, combat, and support operations during World War I.
  • D. World War I naval unit
    A World War I naval unit is a military formation or vessel grouping organized by a nation's navy during the First World War to conduct maritime operations such as convoy escort, blockade enforcement, fleet engagements, and coastal defense.
  • E. United States Army Air Service squadron
    A United States Army Air Service squadron is a military aviation unit of the U.S. Army during and shortly after World War I, responsible for organizing, training, and deploying aircraft and aircrews for combat, reconnaissance, and support missions.
  • 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_69d85cd21dcc81908646251b1c26ea00 completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 3:48 a.m.