Triple

T7924227
Position Surface form Disambiguated ID Type / Status
Subject Vlašim E184019 entity
Predicate hasNearbyCity P350 FINISHED
Object Benešov E227473 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: Benešov | Statement: [Vlašim, hasNearbyCity, Benešov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Benešov
Context triple: [Vlašim, hasNearbyCity, Benešov]
  • A. Benešov chosen
    Benešov is a town in the Czech Republic known as a local administrative and cultural center southeast of Prague.
  • B. Broumov
    Broumov is a historic town in northeastern Bohemia, Czech Republic, known for its Benedictine monastery and proximity to the Broumov Walls sandstone rock formations.
  • C. Blovice
    Blovice is a small town in the Czech Republic that serves as a local administrative and service center in the Plzeň Region.
  • D. Trutnov
    Trutnov is a town in the Czech Republic known as a gateway to the eastern Krkonoše (Giant Mountains) region and for its historical center and industrial heritage.
  • E. Milovice
    Milovice is a town in the Czech Republic known for its rapid post-military redevelopment and location northeast of Prague in the Central Bohemian Region.
  • 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_69ca828fe7bc819090f52c88dcd72183 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3aac02bc8190b13fc354a4fa91d3 completed March 31, 2026, 3:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cf883201d481909efd2f57e852a175 completed April 3, 2026, 9:28 a.m.
Created at: March 30, 2026, 5:06 p.m.