Triple

T17162274
Position Surface form Disambiguated ID Type / Status
Subject Junkers Ju 290 E416509 entity
Predicate derivedFrom P909 FINISHED
Object Junkers Ju 90 NE NERFINISHED

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 90 | Statement: [Junkers Ju 290, derivedFrom, Junkers Ju 90]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Junkers Ju 90
Context triple: [Junkers Ju 290, derivedFrom, Junkers Ju 90]
  • A. Junkers Ju 90 chosen
    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.
  • B. 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.
  • C. Junkers Ju 188
    The Junkers Ju 188 was a German World War II twin‑engine bomber and reconnaissance aircraft developed as an improved, more versatile successor to the Ju 88.
  • D. 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.
  • E. Junkers Ju 52 aircraft
    The Junkers Ju 52 was a German tri-motor transport and bomber aircraft widely used in the 1930s and World War II for troop transport, paratroop drops, and cargo missions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d886d279c081909f8ff1f743ddeb69 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3f91258648190a40396067ba5ecd3 completed April 18, 2026, 9:35 p.m.
Created at: April 10, 2026, 5:37 a.m.