Triple

T16913856
Position Surface form Disambiguated ID Type / Status
Subject LKPR E410270 entity
Predicate locatedNear P294 FINISHED
Object Kladno 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 | Statement: [LKPR, locatedNear, Kladno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kladno
Context triple: [LKPR, locatedNear, Kladno]
  • A. Kladno chosen
    Kladno is an industrial city in the Czech Republic known historically for coal mining and steel production.
  • B. Velenje
    Velenje is a modern industrial town in northern Slovenia known for its coal mining heritage, large lakeside recreational area, and one of the largest Tito statues in the world.
  • C. Ajdovščina
    Ajdovščina is a town in western Slovenia known for its location in the Vipava Valley, strong bora winds, and a mix of Roman heritage and modern industry.
  • D. Gložan
    Gložan is a village in the Vojvodina region of northern Serbia, known for its Slovak ethnic community and agricultural character.
  • E. Sevnica
    Sevnica is a small town in central Slovenia known as the childhood home of former U.S. First Lady Melania Trump.
  • 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3ca3f1a2c8190a512ccc09a080eb4 completed April 18, 2026, 6:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00d458902481908f79cd5a9f72f7fd completed May 10, 2026, 6:54 p.m.
Created at: April 10, 2026, 5:30 a.m.