Triple

T18424597
Position Surface form Disambiguated ID Type / Status
Subject Boeing–Saab E442103 entity
Predicate partner P1136 FINISHED
Object Saab AB 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: Saab AB | Statement: [Boeing–Saab, partner, Saab AB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saab AB
Context triple: [Boeing–Saab, partner, Saab AB]
  • A. Saab AB chosen
    Saab AB is a Swedish aerospace and defense company known for developing military aircraft, advanced defense systems, and security solutions.
  • B. Saab Automobile
    Saab Automobile was a Swedish car manufacturer known for its innovative engineering, turbocharged engines, and distinctive, safety-focused designs.
  • C. Saab Kockums
    Saab Kockums is a Swedish shipyard and defense company best known for designing and building advanced submarines and naval vessels.
  • D. Volvo Cars
    Volvo Cars is a Swedish automotive manufacturer known for its focus on safety, practical design, and premium vehicles.
  • E. Saab XWD
    Saab XWD is Saab’s advanced all-wheel-drive system designed to enhance traction, handling, and stability in various driving conditions.
  • 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_69d8b9eb8a508190a942fd75ebd8b1dc completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e51b1149788190ad7c453547a6e07c completed April 19, 2026, 6:12 p.m.
Created at: April 10, 2026, 10:47 a.m.