Triple

T14347750
Position Surface form Disambiguated ID Type / Status
Subject Eurométropole de Strasbourg E355770 entity
Predicate contains P35 FINISHED
Object Vendenheim E402461 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: Vendenheim | Statement: [Eurométropole de Strasbourg, contains, Vendenheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vendenheim
Context triple: [Eurométropole de Strasbourg, contains, Vendenheim]
  • A. Vendenheim chosen
    Vendenheim is a commune in northeastern France near Strasbourg, known as a regional transport hub and suburban residential area.
  • B. Geinsheim
    Geinsheim is a village and local district of the town Neustadt an der Weinstraße in the German state of Rhineland-Palatinate.
  • C. Leutesheim
    Leutesheim is a village and district of the town of Kehl in the Ortenaukreis region of Baden-Württemberg, Germany, near the Rhine River and the French border.
  • D. Freiolsheim
    Freiolsheim is a village and district of the town of Gaggenau in the Rastatt district of Baden-Württemberg, Germany.
  • E. Passenheim
    Passenheim is the former German name of the town now known as Pasym, located in northeastern Poland’s historic region of Masuria.
  • 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_69d82790a7e08190877e2d349b2e8d8e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8e8d081c8190ac805726a3e98f4c completed April 14, 2026, 6:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb73334c8190a96a92d199c3b101 completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:14 a.m.