Triple

T18392795
Position Surface form Disambiguated ID Type / Status
Subject Svir E449778 entity
Predicate hasTownOnBank P847 FINISHED
Object Podporozhye NE NERFINISHED

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: Podporozhye | Statement: [Svir, hasTownOnBank, Podporozhye]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Podporozhye
Context triple: [Svir, hasTownOnBank, Podporozhye]
  • A. Podporozhye chosen
    Podporozhye is a town in northwestern Russia situated within Leningrad (Saint Petersburg) Oblast, known for its location along the Svir River.
  • B. Pervouralsk
    Pervouralsk is an industrial city in Russia’s Ural region, known for its metallurgical plants and location near the geographic border between Europe and Asia.
  • C. Ustyuzhna
    Ustyuzhna is a historic town in Vologda Oblast, Russia, known for its traditional architecture and role as a local administrative and cultural center.
  • D. Yuzovka
    Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
  • E. Belorechensk
    Belorechensk is a town in Russia’s Krasnodar Krai known for its industrial enterprises and location near the Belaya River in the North Caucasus region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e518435cf481908393c1eb2b4ba659 completed April 19, 2026, 6 p.m.
Created at: April 10, 2026, 10:46 a.m.