Triple

T22072037
Position Surface form Disambiguated ID Type / Status
Subject Bendery E545430 entity
Predicate locatedNear P294 FINISHED
Object Tiraspol 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: Tiraspol | Statement: [Bendery, locatedNear, Tiraspol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tiraspol
Context triple: [Bendery, locatedNear, Tiraspol]
  • A. Tiraspol chosen
    Tiraspol is the de facto capital and largest city of the unrecognized breakaway region of Transnistria in eastern Moldova.
  • B. Chișinău
    Chișinău is the largest city and main political, economic, and cultural center of Moldova.
  • C. Bălți
    Bălți is a major city in northern Moldova, known as an important industrial, cultural, and transportation center often referred to as the country’s "northern capital."
  • D. Soroca
    Soroca is a historic town in northern Moldova known for its well-preserved medieval fortress on the banks of the Dniester River.
  • E. Iași
    Iași is a major cultural, academic, and economic center in northeastern Romania, known for its historic universities, churches, and role as a former capital of the Principality of Moldavia.
  • 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_69e11e344dfc81909b1d88a7221329c7 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12888dcc08190b18d3d44d09ab943 completed April 28, 2026, 9:37 p.m.
Created at: April 16, 2026, 8:28 p.m.