Triple

T5757571
Position Surface form Disambiguated ID Type / Status
Subject Augsburg E127006 entity
Predicate twinCity P1072 FINISHED
Object Liberec E188165 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: Liberec | Statement: [Augsburg, twinCity, Liberec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Liberec
Context triple: [Augsburg, twinCity, Liberec]
  • A. Liberec chosen
    Liberec is a city in the northern Czech Republic known for its textile industry heritage, mountainous surroundings, and the landmark Ještěd Tower.
  • B. Plzeň
    Plzeň is a major city in western Bohemia in the Czech Republic, known for its brewing tradition and industrial heritage.
  • C. Pardubice
    Pardubice is a city in the Czech Republic known for its ice hockey tradition, historic center, and as the hometown of legendary NHL goaltender Dominik Hašek.
  • D. 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.
  • E. Žatec
    Žatec is a historic Czech town in the Ústí nad Labem Region renowned for its long-standing hop-growing tradition and beer production.
  • 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_69c00833a3fc81908f4bc29ed011b7a6 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029084e108190988f1b5f38254007 completed March 22, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1353095c08190b07bcc1299ed7f20 completed March 23, 2026, 12:42 p.m.
Created at: March 22, 2026, 3:49 p.m.