Triple

T4182299
Position Surface form Disambiguated ID Type / Status
Subject Saint Petersburg Oblast E88221 entity
Predicate contains P35 FINISHED
Object Svetogorsk E316280 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: Svetogorsk | Statement: [Saint Petersburg Oblast, contains, Svetogorsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svetogorsk
Context triple: [Saint Petersburg Oblast, contains, Svetogorsk]
  • A. Svetogorsk chosen
    Svetogorsk is a small industrial town in northwestern Russia near the Finnish border, known for its paper mill and location along the Vuoksi River.
  • B. Primorsk
    Primorsk is a port town in northwestern Russia situated on the coast of the Gulf of Finland in Leningrad Oblast.
  • C. Starogard Gdański
    Starogard Gdański is a historic town in northern Poland that serves as an important local industrial and cultural center in the Kociewie region.
  • D. Elbląg
    Elbląg is a historic city in northern Poland known for its reconstructed Old Town, medieval heritage, and role as an important port and industrial center.
  • E. Kotelniki
    Kotelniki is a Moscow Metro station serving as the southeastern terminus of the Tagansko–Krasnopresnenskaya Line in the town of Kotelniki, just outside Moscow.
  • 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_69aed9477e8c81908bcb862d2db55b1d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0305e2e88190a51f176f8534f1f9 completed March 9, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b589fbcc5881908f245bb377082dcc completed March 14, 2026, 4:16 p.m.
Created at: March 9, 2026, 3:45 p.m.