Triple

T17529704
Position Surface form Disambiguated ID Type / Status
Subject Tomahawk E426896 entity
Predicate instanceOf P0 FINISHED
Object aircraft variant name C39065 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: aircraft variant name
Context triple: [Tomahawk, instanceOf, aircraft variant name]
  • A. bomber aircraft variant
    A bomber aircraft variant is a specific version of a bomber designed or modified to perform particular roles, missions, or operate under distinct performance, payload, or technological configurations.
  • B. Boeing 747 variant
    A Boeing 747 variant is a specific model or configuration of the Boeing 747 airliner, distinguished by differences in size, range, engines, avionics, or interior layout tailored to particular airline or mission requirements.
  • C. military trainer aircraft variant
    A military trainer aircraft variant is a modified version of a standard military aircraft specifically adapted with dual controls, simplified systems, or performance changes to safely train pilots and aircrew in operational flying skills.
  • D. stretched airliner variant
    A stretched airliner variant is a lengthened version of an existing aircraft model, typically achieved by adding fuselage sections to increase passenger or cargo capacity while retaining most of the original design and systems.
  • E. Learjet 35 variant
    A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
  • 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
Created at: April 10, 2026, 5:49 a.m.