Triple

T799400
Position Surface form Disambiguated ID Type / Status
Subject Kryvyi Rih E17094 entity
Predicate hasTwinTown P919 FINISHED
Object Ruse E70722 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: Ruse | Statement: [Kryvyi Rih, hasTwinTown, Ruse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruse
Context triple: [Kryvyi Rih, hasTwinTown, Ruse]
  • A. Ruse chosen
    Ruse is a major Bulgarian city and river port on the Danube, known for its elegant architecture and role as an important economic and transport hub.
  • B. Varna
    Varna is a major Bulgarian city on the Black Sea coast known as an important economic, cultural, and maritime center.
  • C. Tarnovo
    Tarnovo, often called Veliko Tarnovo, is a historic Bulgarian city famed as a medieval capital and cultural stronghold, known for its dramatic hillside setting and well-preserved architectural heritage.
  • D. Reutov
    Reutov is a town in western Russia that functions as a suburban satellite of Moscow, known for its residential areas and proximity to the capital.
  • E. Burgas
    Burgas is a major Bulgarian city and industrial center on the Black Sea coast, known for its large seaport and role as a key maritime and logistics hub in the region.
  • 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_69a49378b9c48190adbf5f62e5b7aca1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a7cb26dc8190bdd3a278b8695873 completed March 1, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7c00c1db48190906a02bb80fe98dc completed March 4, 2026, 5:15 a.m.
Created at: March 1, 2026, 7:38 p.m.