Triple

T14157467
Position Surface form Disambiguated ID Type / Status
Subject Lützelau E350848 entity
Predicate hasNameInLanguage P15 FINISHED
Object Lützelau (German) E350848 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: Lützelau (German) | Statement: [Lützelau, hasNameInLanguage, Lützelau (German)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lützelau (German)
Context triple: [Lützelau, hasNameInLanguage, Lützelau (German)]
  • A. Lützelau chosen
    Lützelau is a small, protected island in Lake Zurich, Switzerland, known for its natural beauty, campsite, and recreational facilities.
  • B. Alt-Lichtenberg (German)
    Alt-Lichtenberg (German) is the German name for the Alt-Lichtenberg locality, a district-level area within the Berlin borough of Lichtenberg.
  • C. Lützel
    Lützel is a district of the German city of Koblenz, located on the opposite bank of the Moselle River from the historic city center.
  • D. Langeneß
    Langeneß is a small Hallig island in the Wadden Sea off the coast of Schleswig-Holstein, Germany, known for its low-lying landscape, traditional Frisian culture, and vulnerability to tidal flooding.
  • E. Laußig
    Laußig is a municipality in the German state of Saxony that forms part of the wider Leipzig 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_69d8278775fc8190b0802d22ca2f495d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61377de48190a3470d28f0edd34a completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd193b72f48190b80ac30d32ab8349 completed May 7, 2026, 10:59 p.m.
Created at: April 10, 2026, 12:58 a.m.