Triple

T4628895
Position Surface form Disambiguated ID Type / Status
Subject Junkers Ju 86 E101164 entity
Predicate variant P4680 FINISHED
Object Ju 86E E457226 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 86E | Statement: [Junkers Ju 86, variant, Ju 86E]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ju 86E
Context triple: [Junkers Ju 86, variant, Ju 86E]
  • A. Ju 86D chosen
    The Ju 86D was a German Junkers-built twin‑engine bomber and reconnaissance aircraft variant used by the Luftwaffe in the late 1930s and early World War II.
  • B. Mitsubishi Ki-67
    The Mitsubishi Ki-67 was a twin-engine Japanese World War II medium bomber known for its relatively high speed, maneuverability, and use in a variety of roles including level bombing, torpedo attacks, and kamikaze missions.
  • C. Mitsubishi J8M
    The Mitsubishi J8M was a Japanese World War II rocket-powered interceptor aircraft, developed as a counterpart to Germany’s Messerschmitt Me 163 Komet.
  • D. Kawanishi H8K
    The Kawanishi H8K was a World War II Japanese four-engine flying boat renowned for its long range, heavy armament, and effectiveness in maritime patrol and anti-submarine roles.
  • E. Aichi H9A
    The Aichi H9A was a Japanese World War II-era twin-engine flying boat trainer developed for the Imperial Japanese Navy.
  • 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_69bd43d0497c8190ac23c65c5804846a completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a300e6081909fa9f504aada33ea completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69be03652dc081908abc3e036f853edf completed March 21, 2026, 2:33 a.m.
Created at: March 20, 2026, 1:13 p.m.