Triple

T13765636
Position Surface form Disambiguated ID Type / Status
Subject Duchy of Lauenburg E330732 entity
Predicate significantTown P102273 FINISHED
Object Lauenburg upon Elbe E155306 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: Lauenburg upon Elbe | Statement: [Duchy of Lauenburg, significantTown, Lauenburg upon Elbe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauenburg upon Elbe
Context triple: [Duchy of Lauenburg, significantTown, Lauenburg upon Elbe]
  • A. Lauenburg chosen
    Lauenburg is a historic town in northern Germany situated on the banks of the Elbe River.
  • B. Lauenburg in Pommern
    Lauenburg in Pommern is a historic town in the former Prussian province of Pomerania, now known as Lębork in northern Poland.
  • C. Himmerich
    Himmerich is a hill in Germany’s Siebengebirge range, known for its forested slopes and hiking trails overlooking the Rhine valley.
  • D. Güstrow
    Güstrow is a historic town in northern Germany known for its Renaissance castle, brick Gothic cathedral, and association with sculptor Ernst Barlach.
  • E. Neubrandenburg
    Neubrandenburg is a historic city in northeastern Germany known for its well-preserved medieval brick Gothic architecture and distinctive city wall with multiple gate towers.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0227f2c48190983ccc9395e4e7a2 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd466ac0f08190b99dd4cdcef339c6 completed May 8, 2026, 2:11 a.m.
Created at: April 9, 2026, 10:10 p.m.