Triple

T18535164
Position Surface form Disambiguated ID Type / Status
Subject Tsna River E452945 entity
Predicate hasCityOnBank P7935 FINISHED
Object Morshansk 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: Morshansk | Statement: [Tsna River, hasCityOnBank, Morshansk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morshansk
Context triple: [Tsna River, hasCityOnBank, Morshansk]
  • A. Morshansk chosen
    Morshansk is a historic town in western Russia that developed as a regional trading and administrative center, particularly known for its role in the grain trade during the Imperial era.
  • B. Chuvash
    Chuvash are a Turkic ethnic group native to the Volga region of Russia, known for their distinct Chuvash language and culture.
  • C. Gorno-Mari
    Gorno-Mari is a Uralic Mari language variety spoken by the Hill Mari people in the hilly regions of the Mari El Republic in Russia.
  • D. Dargin
    Dargin is a Northeast Caucasian language spoken primarily by the Dargin people in the Republic of Dagestan in Russia.
  • E. Tatarbunary
    Tatarbunary is a small town in the historical Budjak region of southwestern Ukraine, known for its agricultural surroundings and multiethnic local culture.
  • 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5340193588190ace2c09c6a94cf81 completed April 19, 2026, 7:58 p.m.
Created at: April 10, 2026, 11:37 a.m.