Triple

T8686579
Position Surface form Disambiguated ID Type / Status
Subject Bender E206173 entity
Predicate hasAlternativeName P39 FINISHED
Object Bendery E545430 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: Bendery | Statement: [Bender, hasAlternativeName, Bendery]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bendery
Context triple: [Bender, hasAlternativeName, Bendery]
  • A. Bendery chosen
    Bendery is a historic city in present-day Moldova, known for its strategic fortress on the Dniester River and its long history under various empires, including the Ottoman and Russian empires.
  • B. Pestovo
    Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
  • C. Bogdanovka
    Bogdanovka is a village in Ukraine known as the site of a World War II massacre of Jews and now commemorated as a Holocaust memorial location.
  • D. Bronnitsy
    Bronnitsy is a historic town in Russia known for its jewelry-making traditions and its location southeast of Moscow along the Moskva River.
  • E. Yamburg
    Yamburg is the former name of the Russian town now known as Kingisepp, located in Leningrad Oblast near the border with Estonia.
  • 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_69ca835481fc819084e33d3bc883bfa6 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5730309081909a9a0256c9bf5f8f completed March 31, 2026, 11:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69cef3cd888c81909fb1ece99988db36 completed April 2, 2026, 10:55 p.m.
Created at: March 30, 2026, 6:33 p.m.