Triple

T18395300
Position Surface form Disambiguated ID Type / Status
Subject Petrovgrad E449851 entity
Predicate hasPredecessorName P11166 FINISHED
Object Veliki Bečkerek 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: Veliki Bečkerek | Statement: [Petrovgrad, hasPredecessorName, Veliki Bečkerek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Veliki Bečkerek
Context triple: [Petrovgrad, hasPredecessorName, Veliki Bečkerek]
  • A. Veliki Bečkerek chosen
    Veliki Bečkerek is the former name of the Serbian city now known as Zrenjanin, a regional center in the Banat area of Vojvodina.
  • B. Velika Osojnica
    Velika Osojnica is a scenic hill and viewpoint above Lake Bled in Slovenia, known for its panoramic views of the lake and surrounding Alps.
  • C. Bečva
    Bečva is a river in the eastern Czech Republic that flows through the Moravian region before joining the Morava River.
  • D. Veliki Crljeni
    Veliki Crljeni is a suburban settlement in the Lazarevac municipality near Belgrade, Serbia, known for its proximity to regional coal mining and energy facilities.
  • E. Bosančica
    Bosančica is a historical variant of the Cyrillic script that was used primarily in medieval Bosnia and neighboring regions for writing the Bosnian language.
  • 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e51846bb4c8190990f42a792a78ee0 completed April 19, 2026, 6 p.m.
Created at: April 10, 2026, 10:46 a.m.