Triple

T21787679
Position Surface form Disambiguated ID Type / Status
Subject Southern Sakhalin coast E537882 entity
Predicate hasPortCity P2745 FINISHED
Object Kholmsk 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: Kholmsk | Statement: [Southern Sakhalin coast, hasPortCity, Kholmsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kholmsk
Context triple: [Southern Sakhalin coast, hasPortCity, Kholmsk]
  • A. Kholmsk chosen
    Kholmsk is a port town on the western coast of Sakhalin Island in Russia, serving as an important maritime transport hub in the Sea of Japan.
  • B. Kholmogory
    Kholmogory is a historic Russian town in the Arkhangelsk region that served as an important early northern trading and administrative center.
  • C. Krasnoufimsk
    Krasnoufimsk is a small historic town in Russia’s Ural region, known for its traditional architecture and role as a local administrative and cultural center.
  • D. Nevelsk
    Nevelsk is a small port town on the southwest coast of Sakhalin Island in Russia, facing the Sea of Japan.
  • E. Ozersk
    Ozersk is a closed Russian city in Chelyabinsk Oblast known for its nuclear industry and association with the Mayak production facility.
  • 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_69e0c47198f881908cb0d237266c10e9 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0621c68588190977891055e80a499 completed April 28, 2026, 7:30 a.m.
Created at: April 16, 2026, 6:52 p.m.