Triple

T20053207
Position Surface form Disambiguated ID Type / Status
Subject Bratislava III District E499256 entity
Predicate contains P35 FINISHED
Object Vajnory 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: Vajnory | Statement: [Bratislava III District, contains, Vajnory]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vajnory
Context triple: [Bratislava III District, contains, Vajnory]
  • A. Vajnory chosen
    Vajnory is a borough of Bratislava, Slovakia, known for its village-like character, traditional architecture, and proximity to the city’s northeastern outskirts.
  • B. Ozerne
    Ozerne is a settlement located on the shores of Lake Yalpuh in southwestern Ukraine.
  • C. Bochorna
    Bochorna is a remote highland village in the Tusheti region of northeastern Georgia, known as one of the highest permanently inhabited settlements in Europe.
  • D. Pavoloch
    Pavoloch is a historic settlement in present-day Ukraine, known for its role in the Polish–Lithuanian Commonwealth era and as the place where nobleman Jeremi Wiśniowiecki died.
  • E. Huczwa
    Huczwa is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
  • 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_69da6276bcf48190aabbf279192a5fb4 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6633043a481908359ad232607182a completed April 20, 2026, 5:32 p.m.
Created at: April 11, 2026, 3:38 p.m.