Triple

T5008687
Position Surface form Disambiguated ID Type / Status
Subject Airco DH.9 E112559 entity
Predicate derivedFrom P909 FINISHED
Object Airco DH.4 E20407 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Airco DH.4 | Statement: [Airco DH.9, derivedFrom, Airco DH.4]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Airco DH.4
Context triple: [Airco DH.9, derivedFrom, Airco DH.4]
  • A. Airco DH.4 chosen
    The Airco DH.4 was a British World War I two-seat day bomber and reconnaissance aircraft widely used by both the Royal Flying Corps and later the Royal Air Force.
  • B. Airco DH.2
    The Airco DH.2 was a British single-seat pusher biplane fighter of World War I, notable as one of the first effective Allied aircraft designed specifically to counter the Fokker Eindecker.
  • C. Airco DH.5
    The Airco DH.5 was a British World War I single-seat biplane fighter notable for its unusual backward-staggered wings and limited operational success.
  • D. Airco DH.6
    The Airco DH.6 was a British single-engine biplane widely used as a basic trainer aircraft during World War I.
  • E. Airco DH.1
    The Airco DH.1 was a British two-seat pusher biplane reconnaissance and fighter aircraft used early in World War I.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69bd4433d0b08190877e83959ef40d81 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd72eb05f881908d7dc3d7cd07b2ae completed March 20, 2026, 4:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf832e0da88190aa6b09dd88fb6157 completed March 22, 2026, 5:50 a.m.
Created at: March 20, 2026, 1:35 p.m.