Triple

T19900814
Position Surface form Disambiguated ID Type / Status
Subject Plzeň–Klatovy railway line E478281 entity
Predicate connects P390 FINISHED
Object city of Plzeň NE NERFINISHED

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: city of Plzeň | Statement: [Plzeň–Klatovy railway line, connects, city of Plzeň]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Plzeň
Context triple: [Plzeň–Klatovy railway line, connects, city of Plzeň]
  • A. Plzeň chosen
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
  • B. Kolín
    Kolín is a historic industrial town and important transport hub on the Elbe River in the Central Bohemian Region of the Czech Republic.
  • C. České Budějovice
    České Budějovice is a historic city in the Czech Republic known for its medieval architecture and as the original home of Budweiser Budvar beer.
  • D. Žatec
    Žatec is a historic Czech town in the Ústí nad Labem Region renowned for its long-standing hop-growing tradition and beer production.
  • E. Moravské Budějovice
    Moravské Budějovice is a small historic town in the Czech Republic known for its traditional architecture and regional cultural heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e520682081909892916424699bd5 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65941977081909e2f94724eb2c3c0 completed April 20, 2026, 4:50 p.m.
Created at: April 10, 2026, 1:52 p.m.