Triple

T13388191
Position Surface form Disambiguated ID Type / Status
Subject Lansen E319499 entity
Predicate predecessor P97 FINISHED
Object Saab 18 E322162 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: Saab 18 | Statement: [Lansen, predecessor, Saab 18]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saab 18
Context triple: [Lansen, predecessor, Saab 18]
  • A. Saab 18 chosen
    The Saab 18 was a Swedish twin-engine bomber and reconnaissance aircraft used by the Swedish Air Force during and after World War II.
  • B. Saab 105
    The Saab 105 is a Swedish twin-engine jet trainer and light attack aircraft introduced in the 1960s and used primarily by the Swedish Air Force.
  • C. Saab 210 Lilldraken
    The Saab 210 "Lilldraken" was a Swedish experimental jet aircraft used as a scaled testbed to develop and refine the distinctive double-delta wing design later employed on the Saab 35 Draken fighter.
  • D. Saab 2000
    The Saab 2000 is a high-speed twin‑engine turboprop regional airliner developed in the 1990s, known for its fast cruise performance and efficient short- to medium-haul operations.
  • E. Saab 340
    The Saab 340 is a twin‑engine turboprop regional airliner widely used for short-haul passenger services around the world.
  • 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_69d806b886bc8190b676e7768b8e01c5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dba0d3a40081909ba49556130ad0e7 completed April 12, 2026, 1:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7b058bc688190b3549d1cac6f4576 completed May 3, 2026, 8:30 p.m.
Created at: April 9, 2026, 9:34 p.m.