Triple

T19905014
Position Surface form Disambiguated ID Type / Status
Subject Yak-1 E478389 entity
Predicate successor P78 FINISHED
Object Yak-3 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: Yak-3 | Statement: [Yak-1, successor, Yak-3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yak-3
Context triple: [Yak-1, successor, Yak-3]
  • A. Yakovlev Yak-3 chosen
    The Yakovlev Yak-3 was a highly maneuverable Soviet World War II fighter aircraft renowned for its excellent performance at low altitudes and effectiveness on the Eastern Front.
  • B. Yak-1
    The Yak-1 was a Soviet single-seat fighter aircraft of World War II, noted for its agility and major role in early Eastern Front air combat.
  • C. Yakovlev Yak-9
    The Yakovlev Yak-9 was a versatile Soviet World War II fighter aircraft widely used on the Eastern Front in roles ranging from air superiority to ground attack.
  • D. Yakovlev Yak-11
    The Yakovlev Yak-11 is a Soviet two-seat advanced trainer aircraft developed in the late 1940s, widely used for pilot training and later popular in civilian warbird circles.
  • E. Yakovlev Yak-23
    The Yakovlev Yak-23 is a Soviet early-generation jet fighter developed in the late 1940s, known for its simple design, straight wings, and use as a lightweight, agile interceptor during the early Cold War.
  • 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_69d8e520682081909892916424699bd5 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65945cc2081908224902d5f042d7a completed April 20, 2026, 4:50 p.m.
Created at: April 10, 2026, 1:52 p.m.