Triple

T17473672
Position Surface form Disambiguated ID Type / Status
Subject Laupheim Air Base E425482 entity
Predicate locatedIn P40 FINISHED
Object Laupheim 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: Laupheim | Statement: [Laupheim Air Base, locatedIn, Laupheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laupheim
Context triple: [Laupheim Air Base, locatedIn, Laupheim]
  • A. Laupheim chosen
    Laupheim is a town in the district of Biberach in the German state of Baden-Württemberg, known historically for its Jewish community and as an industrial and cultural center in Upper Swabia.
  • B. Blaubeuren
    Blaubeuren is a historic town in the Alb-Donau district of Baden-Württemberg, Germany, known for its medieval old town and the karst spring Blautopf.
  • C. Gerlachsheim
    Gerlachsheim is a district of the town Lauda-Königshofen in the Main-Tauber-Kreis region of Baden-Württemberg, Germany.
  • D. Mainstockheim
    Mainstockheim is a small municipality in the Franconian region of northern Bavaria, Germany, situated along the Main River and known for its winegrowing tradition.
  • E. Schwanau
    Schwanau is a municipality in southwestern Germany’s Baden-Württemberg region, situated near the Rhine River and the French border.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451b990848190b2e8510d67e94b79 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:47 a.m.