Triple

T17999347
Position Surface form Disambiguated ID Type / Status
Subject Lemgo E430583 entity
Predicate hasLandmark P105 FINISHED
Object Rathaus Lemgo 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: Rathaus Lemgo | Statement: [Lemgo, hasLandmark, Rathaus Lemgo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rathaus Lemgo
Context triple: [Lemgo, hasLandmark, Rathaus Lemgo]
  • A. Rathaus Lemgo chosen
    Rathaus Lemgo is the historic town hall of Lemgo, Germany, renowned for its distinctive Weser Renaissance architecture and central role in the city’s civic life.
  • B. Lünen Town Hall
    Lünen Town Hall is the central municipal building and administrative seat of the city of Lünen in North Rhine-Westphalia, Germany.
  • C. Lemgo, Germany
    Lemgo, Germany is a historic town in the Lippe district of North Rhine-Westphalia known for its well-preserved medieval and Renaissance architecture.
  • D. Lüneburg Town Hall
    Lüneburg Town Hall is a historic and architecturally significant city hall in Lüneburg, Germany, renowned for its medieval and baroque elements.
  • E. Bramsche town hall
    Bramsche town hall is the central municipal building that houses the local government and administrative offices of the town of Bramsche in Lower Saxony, Germany.
  • 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_69d8b90364248190a37381adea932f42 completed April 10, 2026, 8:46 a.m.
NER Named-entity recognition batch_69e4b3e75e908190a6ff6a3ec6069ff5 completed April 19, 2026, 10:52 a.m.
Created at: April 10, 2026, 10:23 a.m.