Triple

T14561639
Position Surface form Disambiguated ID Type / Status
Subject Strasbourg bus network E341679 entity
Predicate hasHub P2413 FINISHED
Object Lingolsheim E1116622 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: Lingolsheim | Statement: [Strasbourg bus network, hasHub, Lingolsheim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lingolsheim
Context triple: [Strasbourg bus network, hasHub, Lingolsheim]
  • A. Lingolsheim chosen
    Lingolsheim is a suburban commune in northeastern France, located just southwest of Strasbourg in the Grand Est region.
  • B. Guebwiller
    Guebwiller is a commune in northeastern France known for its wine production and location at the foot of the Vosges mountains in the Alsace region.
  • C. Molsheim
    Molsheim is a historic town in northeastern France’s Grand Est region, known for its medieval architecture and as the birthplace of the Bugatti automobile brand.
  • D. Souffelweyersheim
    Souffelweyersheim is a suburban commune in northeastern France, located near Strasbourg in the Grand Est region.
  • E. Fegersheim
    Fegersheim is a commune in northeastern France, located in the Bas-Rhin department within the Strasbourg metropolitan area.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb389d0f48190a1d9d69456d1cbe1 completed April 14, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b3da8f08190b70b08532dfc22ba completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:23 a.m.