Triple

T15812200
Position Surface form Disambiguated ID Type / Status
Subject Sambia Peninsula E383381 entity
Predicate containsSettlement P847 FINISHED
Object Svetlogorsk E503539 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: Svetlogorsk | Statement: [Sambia Peninsula, containsSettlement, Svetlogorsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svetlogorsk
Context triple: [Sambia Peninsula, containsSettlement, Svetlogorsk]
  • A. Svetlogorsk chosen
    Svetlogorsk is a coastal resort town on the Baltic Sea in Russia’s Kaliningrad Oblast, known for its beaches, sanatoriums, and picturesque seaside promenade.
  • B. Svetlogorsk
    Svetlogorsk is an industrial city in southeastern Belarus known for its chemical and pulp-and-paper industries along the Berezina River.
  • C. Perovo
    Perovo is a Moscow Metro station serving the Kalininsko–Solntsevskaya Line in the Perovo District of eastern Moscow.
  • D. Svetogorsk
    Svetogorsk is a small industrial town in northwestern Russia near the Finnish border, known for its paper mill and location along the Vuoksi River.
  • E. Dravograd
    Dravograd is a small Slovenian town in the Carinthia region, known for its location at the confluence of the Drava and Meža rivers and its historical role as a regional center.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52bbb888190b226567e84ced7e9 completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff9993c86c8190b1d106af7537080a completed May 9, 2026, 8:31 p.m.
Created at: April 10, 2026, 4:49 a.m.