Triple

T11704066
Position Surface form Disambiguated ID Type / Status
Subject Felvidék E278196 entity
Predicate containsHistoricalCity P43430 FINISHED
Object Nagyszombat E126688 NE FINISHED

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: Nagyszombat | Statement: [Felvidék, containsHistoricalCity, Nagyszombat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nagyszombat
Context triple: [Felvidék, containsHistoricalCity, Nagyszombat]
  • A. 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.
  • B. Pozsony chosen
    Pozsony is the historical Hungarian name for the city now known as Bratislava, the capital of Slovakia.
  • C. Nové Mesto nad Váhom
    Nové Mesto nad Váhom is a town in western Slovakia known for its location in the Váh River valley and its regional administrative and economic role.
  • D. 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aaff2ce88190b4a1e4b341ad5377 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a49b1080819096593733ee48a187 completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69f6a52fcfa081909cc312a56bf12693 completed May 3, 2026, 1:30 a.m.
Created at: April 8, 2026, 9:40 p.m.