Triple

T9765165
Position Surface form Disambiguated ID Type / Status
Subject Slaný E236768 entity
Predicate locatedIn P40 FINISHED
Object Kladno District E181630 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: Kladno District | Statement: [Slaný, locatedIn, Kladno District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kladno District
Context triple: [Slaný, locatedIn, Kladno District]
  • A. Brčko District
    Brčko District is a self-governing, multi-ethnic administrative unit in northeastern Bosnia and Herzegovina that holds a strategically important position along the Sava River.
  • B. Kladno chosen
    Kladno is an industrial city in the Czech Republic known historically for coal mining and steel production.
  • C. Bytča District
    Bytča District is an administrative district in the Žilina Region of northwestern Slovakia, known for its small towns and historical architecture.
  • D. Rakovník District
    Rakovník District is an administrative district in the Central Bohemian Region of the Czech Republic, known for its historic town of Rakovník and a mix of agricultural and forested landscapes.
  • E. County of Kladsko
    The County of Kladsko was a historically contested border region in Central Europe, centered on the town of Kłodzko, that shifted between Bohemian, Austrian, and Prussian control.
  • 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_69ca84d64f6c8190a4ed4e9f5936eda5 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0a040988190b1c940f9e5c42f9c completed April 1, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcf965e88190b505ce160f77e9b7 completed April 5, 2026, 1:38 a.m.
Created at: March 30, 2026, 8:25 p.m.