Triple

T4128729
Position Surface form Disambiguated ID Type / Status
Subject BMW 801 E84988 entity
Predicate usedInAircraft P10706 FINISHED
Object Junkers Ju 188 E431593 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: Junkers Ju 188 | Statement: [BMW 801, usedInAircraft, Junkers Ju 188]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Junkers Ju 188
Context triple: [BMW 801, usedInAircraft, Junkers Ju 188]
  • A. Junkers Ju 290
    The Junkers Ju 290 was a large German long-range transport and maritime patrol aircraft used by the Luftwaffe during World War II.
  • B. Junkers Ju 388 chosen
    The Junkers Ju 388 was a late-World War II German high-altitude bomber and reconnaissance aircraft developed from the Ju 188, designed to counter Allied bomber formations and operate above enemy fighter range.
  • C. Junkers Ju 88
    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.
  • D. Junkers Ju 90
    The Junkers Ju 90 was a German four‑engine airliner of the late 1930s that was later adapted for military transport roles during World War II.
  • 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_69aed935ccd881909dc61f81bcdb7a78 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af021c5ca48190a829bab07dda55d0 completed March 9, 2026, 5:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69be395356e88190ba6c4b228669e40c completed March 21, 2026, 6:23 a.m.
Created at: March 9, 2026, 3:42 p.m.