Triple

T14437772
Position Surface form Disambiguated ID Type / Status
Subject Zoppot E358008 entity
Predicate hasNameInGerman P22792 FINISHED
Object Zoppot E358008 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: Zoppot | Statement: [Zoppot, hasNameInGerman, Zoppot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zoppot
Context triple: [Zoppot, hasNameInGerman, Zoppot]
  • A. Zoppot chosen
    Zoppot is the German name for the Baltic Sea resort city of Sopot, now located in northern Poland between Gdańsk and Gdynia.
  • B. Perasdorf
    Perasdorf is a small municipality in the Straubing-Bogen district of Lower Bavaria, Germany.
  • C. Buchach
    Buchach is a historic town in western Ukraine, known for its multicultural past and as the birthplace of several notable Jewish intellectuals and writers.
  • D. Kurzberg
    Kurzberg is a surname of German origin, likely derived from geographic or topographic roots.
  • E. Varnsdorf
    Varnsdorf is a town in the northern Czech Republic near the German border, known historically for its textile industry and multicultural character.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de914a45ec81909ab8ccf302047d7f completed April 14, 2026, 7:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bd7f46881908df1a1cea7b6af9b completed May 8, 2026, 3:43 a.m.
Created at: April 10, 2026, 1:18 a.m.