Triple

T349487
Position Surface form Disambiguated ID Type / Status
Subject Junkers Ju 88 E7409 entity
Predicate notableVariant P4680 FINISHED
Object Ju 88G E7409 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: Ju 88G | Statement: [Junkers Ju 88, notableVariant, Ju 88G]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ju 88G
Context triple: [Junkers Ju 88, notableVariant, Ju 88G]
  • A. Junkers Ju 88 chosen
    The Junkers Ju 88 was a highly versatile German World War II twin‑engine aircraft used extensively as a bomber, dive bomber, night fighter, and reconnaissance plane.
  • B. Heinkel He 219
    The Heinkel He 219 was a German World War II twin-engine night fighter aircraft notable for its advanced radar equipment and effectiveness against Allied bombers.
  • C. Messerschmitt Bf 110
    The Messerschmitt Bf 110 was a German twin-engine heavy fighter and fighter-bomber used extensively during World War II in roles including long-range escort, ground attack, and night fighting.
  • D. Arado Ar 234
    The Arado Ar 234 was a German World War II jet-powered bomber and reconnaissance aircraft, notable as the world’s first operational jet bomber.
  • E. Heinkel He 177
    The Heinkel He 177 was a German long-range heavy bomber of World War II, notable for its troubled development, engine reliability issues, and limited operational success.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb1dc5f88190b54d084c6def7fc5 completed Feb. 28, 2026, 1:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69a431dbb77081908f87740c9b827f90 completed March 1, 2026, 12:32 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.