Triple

T5332491
Position Surface form Disambiguated ID Type / Status
Subject Sellin E123341 entity
Predicate locatedNear P294 FINISHED
Object Göhren E196316 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: Göhren | Statement: [Sellin, locatedNear, Göhren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Göhren
Context triple: [Sellin, locatedNear, Göhren]
  • A. Göhren chosen
    Göhren is a seaside resort town on the Baltic Sea coast of Germany, located on the island of Rügen and known for its beaches and tourism.
  • B. Gehren
    Gehren is a small town in the German state of Thuringia, historically notable as the birthplace of Maria Barbara Bach, first wife of composer Johann Sebastian Bach.
  • C. Radevormwald
    Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
  • D. Rheydt
    Rheydt is a district of the German city of Mönchengladbach in North Rhine-Westphalia, historically an independent town in the Rhineland.
  • E. Hasselwerder
    Hasselwerder is a small island located in Lake Tegel in Berlin, Germany.
  • 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_69bd46477f9081909d242a327d749466 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd85aab0308190990626cbc9da3e21 completed March 20, 2026, 5:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf18b75c388190955e4e31d71ffedb completed March 21, 2026, 10:16 p.m.
Created at: March 20, 2026, 2 p.m.