Triple

T7908783
Position Surface form Disambiguated ID Type / Status
Subject Moravian Karst E183644 entity
Predicate nearbyTown P3883 FINISHED
Object Blansko E429605 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: Blansko | Statement: [Moravian Karst, nearbyTown, Blansko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Blansko
Context triple: [Moravian Karst, nearbyTown, Blansko]
  • A. Blansko chosen
    Blansko is a small industrial town in the South Moravian Region of the Czech Republic, known as a gateway to the Moravian Karst cave system.
  • B. Bednja
    Bednja is a river in northern Croatia that flows through the Zagorje region before joining the Drava River.
  • C. Husinec
    Husinec is a small Czech town best known as the birthplace of the religious reformer Jan Hus.
  • D. Kapesovo
    Kapesovo is a traditional stone-built village in the Zagori region of Epirus, Greece, known for its preserved architecture and scenic mountainous setting.
  • E. Osek
    Osek is a town in the Czech Republic historically associated with the family origins of writer Franz Kafka’s father, Hermann Kafka.
  • 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_69ca828dec0c81908b8f55a4dbbb53ff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a5c85ac81908de2ca387826ea2f completed March 31, 2026, 3:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbdfe21f9081909d45565867ac7436 completed March 31, 2026, 2:53 p.m.
Created at: March 30, 2026, 5:03 p.m.