Triple

T15058886
Position Surface form Disambiguated ID Type / Status
Subject Strasbourg Airport E379569 entity
Predicate locatedIn P40 FINISHED
Object Entzheim E398892 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: Entzheim | Statement: [Strasbourg Airport, locatedIn, Entzheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Entzheim
Context triple: [Strasbourg Airport, locatedIn, Entzheim]
  • A. Entzheim chosen
    Entzheim is a commune in northeastern France, near Strasbourg, best known for hosting Strasbourg Airport.
  • B. Marlenheim
    Marlenheim is a commune in northeastern France’s Alsace region, known as a historic wine-producing village and gateway to the area’s renowned vineyards and scenic countryside.
  • C. Ettenheim
    Ettenheim is a historic small town in southwestern Germany’s Baden-Württemberg region, known for its well-preserved old town and location near the Black Forest.
  • D. Meisenthal
    Meisenthal is a village in northeastern France renowned for its historic glassmaking tradition and cultural heritage.
  • E. Balzhausen
    Balzhausen is a small municipality in the Bavarian region of Swabia in southern Germany.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69dedee50afc8190bf7b0f4bbe8c60a3 completed April 15, 2026, 12:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69fffee31b70819092d0583100a7101a completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 3:01 a.m.