Triple

T4527132
Position Surface form Disambiguated ID Type / Status
Subject Svir River E106206 entity
Predicate hasSettlementOnBanks P57254 FINISHED
Object Podporozhye E450488 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: Podporozhye | Statement: [Svir River, hasSettlementOnBanks, Podporozhye]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Podporozhye
Context triple: [Svir River, hasSettlementOnBanks, 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. Otradnoye
    Otradnoye is a town in Russia located within the Leningrad (Saint Petersburg) region, known for its position along the Neva River and proximity to Saint Petersburg.
  • C. Otradnoye
    Otradnoye is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line serving the Otradnoye District in northern Moscow.
  • D. Verkhnedneprovsk
    Verkhnedneprovsk is a town in central Ukraine, historically part of the Dnipropetrovsk region, known for its location near the confluence of the Samotkan and Dnieper rivers.
  • E. Skovorodino
    Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
  • 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_69bd43f3d6e08190a91824f833d51bbe completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6231856c8190be9386a0ae15e7cf completed March 20, 2026, 3:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69be6f8abc3481909dbb42ddde2729ca completed March 21, 2026, 10:14 a.m.
Created at: March 20, 2026, 1:03 p.m.