Triple

T8336753
Position Surface form Disambiguated ID Type / Status
Subject Tuapse E195806 entity
Predicate hasRailwayConnectionTo P3791 FINISHED
Object Krasnodar E175511 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: Krasnodar | Statement: [Tuapse, hasRailwayConnectionTo, Krasnodar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krasnodar
Context triple: [Tuapse, hasRailwayConnectionTo, Krasnodar]
  • A. Krasnodar chosen
    Krasnodar is a major city in southern Russia, serving as the administrative center of Krasnodar Krai and an important economic and cultural hub of the region.
  • B. Rostova
    Rostova is a Russian surname best known from Leo Tolstoy’s novel "War and Peace," where it is borne by members of the central Rostov family.
  • C. Stavropol
    Stavropol is a major administrative, cultural, and economic center in southwestern Russia, serving as the capital of Stavropol Krai in the North Caucasus region.
  • D. Volgograd
    Volgograd is a major city in southwestern Russia on the Volga River, historically known as Stalingrad and renowned as the site of one of World War II’s most pivotal and brutal battles.
  • E. Rostov
    Rostov is one of Russia’s oldest and most historically significant towns, renowned for its well-preserved kremlin and traditional architecture.
  • 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd3fc80819097b326119107ad4d completed March 31, 2026, 8:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc71005f0819092c46fa5a43f2a15 completed April 2, 2026, 1:32 a.m.
Created at: March 30, 2026, 5:57 p.m.