Triple

T11969772
Position Surface form Disambiguated ID Type / Status
Subject Lębork E284885 entity
Predicate hasGermanName P1435 FINISHED
Object Lauenburg in Pommern E158892 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 in Pommern | Statement: [Lębork, hasGermanName, Lauenburg in Pommern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauenburg in Pommern
Context triple: [Lębork, hasGermanName, Lauenburg in Pommern]
  • A. Lauenburg in Pommern chosen
    Lauenburg in Pommern is a historic town in the former Prussian province of Pomerania, now known as Lębork in northern Poland.
  • B. Lauenburg
    Lauenburg is a historic town in northern Germany situated on the banks of the Elbe River.
  • C. Pomerania-Wolgast
    Pomerania-Wolgast was a medieval duchy in the Holy Roman Empire, centered around the town of Wolgast and ruled by a branch of the House of Griffins as part of the partitioned Duchy of Pomerania.
  • D. Teterow
    Teterow is a small historic town in northeastern Germany known for its medieval architecture and location in the Mecklenburg Lake District.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9037bee54819085242a3ef3e286f9 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f459691ff0819099282172933d2d81 completed May 1, 2026, 7:42 a.m.
Created at: April 8, 2026, 9:46 p.m.