Triple

T12245251
Position Surface form Disambiguated ID Type / Status
Subject Koło E291833 entity
Predicate hasGermanName P1435 FINISHED
Object Warthbrücken E291833 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: Warthbrücken | Statement: [Koło, hasGermanName, Warthbrücken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Warthbrücken
Context triple: [Koło, hasGermanName, Warthbrücken]
  • A. Warthbrücken chosen
    Warthbrücken is the German name for the Polish town of Koło, located in central Poland on the Warta River.
  • B. Kindelbrück
    Kindelbrück is a small town in the German state of Thuringia, situated in the Unstrut river valley and known for its rural character and historical architecture.
  • C. Königsbrück
    Königsbrück is a small town in the Free State of Saxony in eastern Germany, known for its historic architecture and proximity to the Königsbrück Heath nature reserve.
  • D. Quaibrücke
    Quaibrücke is a prominent road and tram bridge in central Zurich, Switzerland, connecting the old town with the lakeside area where the Limmat River flows out of Lake Zurich.
  • E. Bersenbrück
    Bersenbrück is a small town in Lower Saxony, Germany, known for its historic abbey and its location on the river Hase.
  • 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_69d6ab67950c8190be08450a06228c4b completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb893a08190bbdfcb23082b8f34 completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60ab7b9308190b621b71d75aa10cc completed May 2, 2026, 2:31 p.m.
Created at: April 8, 2026, 9:51 p.m.