Triple

T18395317
Position Surface form Disambiguated ID Type / Status
Subject Petrovgrad E449851 entity
Predicate replaced P101 FINISHED
Object toponym 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: toponym Veliki Bečkerek | Statement: [Petrovgrad, replaced, toponym Veliki Bečkerek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: toponym Veliki Bečkerek
Context triple: [Petrovgrad, replaced, toponym Veliki Bečkerek]
  • A. Bečva
    Bečva is a river in the eastern Czech Republic that flows through the Moravian region before joining the Morava River.
  • B. Novi Bečej
    Novi Bečej is a town in northern Serbia’s Vojvodina region, known for its location on the Tisa River and its agricultural and cultural significance.
  • C. Bečkerek chosen
    Bečkerek is the historical name of the Serbian city now known as Zrenjanin, located in the Banat region of the Vojvodina province.
  • D. 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.
  • E. Kamenica nad Cirochou
    Kamenica nad Cirochou is a village and municipality in eastern Slovakia, known for its rural character and local cultural traditions.
  • 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.