Triple

T10691805
Position Surface form Disambiguated ID Type / Status
Subject Graudenz E252028 entity
Predicate germanNameOf P22792 FINISHED
Object Grudziądz E1094460 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: Grudziądz | Statement: [Graudenz, germanNameOf, Grudziądz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grudziądz
Context triple: [Graudenz, germanNameOf, Grudziądz]
  • A. Grudziądz chosen
    Grudziądz is a historic city in northern Poland on the Vistula River, known for its medieval granaries and well-preserved Old Town.
  • B. Gorzów Wielkopolski
    Gorzów Wielkopolski is a city in western Poland, known as one of the two capitals of the Lubusz Voivodeship and an important regional industrial and cultural center.
  • C. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • D. Ogrodzieniec
    Ogrodzieniec is a town in southern Poland best known for the ruins of its medieval castle in the Kraków-Częstochowa Upland.
  • E. Wałcz
    Wałcz is a town in northwestern Poland known for its lakes, forests, and role as a local administrative and cultural center.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fd3705788190bcbdef93b4c5f574 completed April 9, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bab66488190a465e40f1181506e completed May 8, 2026, 3:42 a.m.
Created at: April 8, 2026, 9:11 p.m.