Triple

T15947608
Position Surface form Disambiguated ID Type / Status
Subject Lauingen E386724 entity
Predicate locatedNear P294 FINISHED
Object Gundelfingen an der Donau E789105 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: Gundelfingen an der Donau | Statement: [Lauingen, locatedNear, Gundelfingen an der Donau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gundelfingen an der Donau
Context triple: [Lauingen, locatedNear, Gundelfingen an der Donau]
  • A. Gundelfingen an der Donau chosen
    Gundelfingen an der Donau is a small Bavarian town in southern Germany situated on the Danube River.
  • B. Gundelfingen
    Gundelfingen is a municipality in southwestern Germany, located near Freiburg im Breisgau in the state of Baden-Württemberg.
  • C. Friedlingen
    Friedlingen is a district of the German town Weil am Rhein, located in the far southwest of Baden-Württemberg near the borders with France and Switzerland.
  • D. Truchtelfingen
    Truchtelfingen is a former independent locality in Baden-Württemberg, Germany, that now forms part of the town of Albstadt.
  • E. Vilshofen an der Donau
    Vilshofen an der Donau is a Bavarian town on the Danube River known for its historic old town and role as a regional commercial and cultural center.
  • 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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156d2fda8819085279d2a0f8a02ab completed April 16, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb5c0c8a481908aa7a40bca15e38e completed May 9, 2026, 10:31 p.m.
Created at: April 10, 2026, 4:53 a.m.