Triple

T15023239
Position Surface form Disambiguated ID Type / Status
Subject Sopot City Council E378138 entity
Predicate legislativeBodyFor P239 FINISHED
Object city of Sopot E77811 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: city of Sopot | Statement: [Sopot City Council, legislativeBodyFor, city of Sopot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Sopot
Context triple: [Sopot City Council, legislativeBodyFor, city of Sopot]
  • A. Sopot
    Sopot is a suburban municipality of Belgrade, Serbia, known for its rural character and proximity to the Avala and Kosmaj mountains.
  • B. Sopot chosen
    Sopot is a Polish Baltic Sea resort city famous for its sandy beaches, long wooden pier, and vibrant spa and nightlife culture.
  • C. Serock
    Serock is a locality situated near the Western Bug River in eastern Europe.
  • D. Gdańsk
    Gdańsk is a major Polish port city on the Baltic Sea, known for its rich Hanseatic history, shipyards, and role in the origins of the Solidarity movement.
  • E. Kamień Pomorski
    Kamień Pomorski is a historic town in north-western Poland known for its medieval architecture, spa traditions, and location near the Baltic Sea.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7de117c8190a1b9fa8d1602057e completed April 15, 2026, 12:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff908410548190ada5d4f71d52919b completed May 9, 2026, 7:52 p.m.
Created at: April 10, 2026, 2:56 a.m.