Triple

T20887010
Position Surface form Disambiguated ID Type / Status
Subject Ružinov E514308 entity
Predicate contains P35 FINISHED
Object Trnávka 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: Trnávka | Statement: [Ružinov, contains, Trnávka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Trnávka
Context triple: [Ružinov, contains, Trnávka]
  • A. Trnávka chosen
    Trnávka is a neighborhood of Bratislava, Slovakia, situated within the Ružinov borough and known for its mix of residential areas and light industry.
  • B. Trstená
    Trstená is a small town in northern Slovakia near the Polish border, known for its proximity to the Orava Reservoir and the Orava region’s natural landscapes.
  • C. Třemošná
    Třemošná is a small town in the western Czech Republic, located near the city of Plzeň in the Plzeň Region.
  • D. Terchová
    Terchová is a Slovak village in the Malá Fatra mountains known as the birthplace of the legendary outlaw Juraj Jánošík and for its rich folk traditions and natural scenery.
  • E. Třebeň
    Třebeň is a small municipality and village in the Karlovy Vary Region of the Czech Republic.
  • 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_69e0b4f733f081908a401c0b7beb0b9f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6d058d4dc81908398f8c75e30dc77 completed April 21, 2026, 1:18 a.m.
Created at: April 16, 2026, 12:46 p.m.