Triple

T20168309
Position Surface form Disambiguated ID Type / Status
Subject Central Bratislava E491885 entity
Predicate locatedIn P40 FINISHED
Object Bratislava 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: Bratislava | Statement: [Central Bratislava, locatedIn, Bratislava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bratislava
Context triple: [Central Bratislava, locatedIn, Bratislava]
  • A. Bratislava chosen
    Bratislava is the capital and largest city of Slovakia, situated along the Danube River near the borders with Austria and Hungary.
  • B. Košice
    Košice is a major city in eastern Slovakia known for its historic Old Town, Gothic St. Elisabeth Cathedral, and role as an important cultural and economic center.
  • C. Banská Bystrica
    Banská Bystrica is a historic central Slovak city best known as the main center of the anti-Nazi Slovak National Uprising during World War II.
  • D. Trenčín
    Trenčín is a historic city in western Slovakia known for its medieval castle overlooking the Váh River and its role as a regional cultural and economic center.
  • E. Kežmarok
    Kežmarok is a historic town in northern Slovakia known for its well-preserved medieval architecture and role as a cultural center of the Spiš (Spisz) region.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66845cb588190820c50eea0c40d83 completed April 20, 2026, 5:54 p.m.
Created at: April 11, 2026, 11:35 p.m.