Triple

T12415401
Position Surface form Disambiguated ID Type / Status
Subject Principality of Karvuna E296622 entity
Predicate hadPort P2745 FINISHED
Object Varna E41324 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: Varna | Statement: [Principality of Karvuna, hadPort, Varna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Varna
Context triple: [Principality of Karvuna, hadPort, Varna]
  • A. Varna chosen
    Varna is a major Bulgarian city on the Black Sea coast known as an important economic, cultural, and maritime center.
  • B. Ruse
    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.
  • C. Silistra
    Silistra is a historic city in northeastern Bulgaria on the Danube River, known as an important cultural and economic center of the Dobruja region.
  • D. Shumen
    Shumen is a city in northeastern Bulgaria known for its historical significance, including nearby medieval capitals and the Monument to 1300 Years of Bulgaria.
  • E. 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.
  • 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_69d6ad9f464c81909db36d7e96e34b9e completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d6c4f6c8190bc99d3f7b64205c3 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68ea3ec588190bca355953267578f completed May 2, 2026, 11:54 p.m.
Created at: April 8, 2026, 9:55 p.m.