Triple

T14572842
Position Surface form Disambiguated ID Type / Status
Subject Piła E341962 entity
Predicate formerName P65 FINISHED
Object Schneidemühl E857292 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: Schneidemühl | Statement: [Piła, formerName, Schneidemühl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schneidemühl
Context triple: [Piła, formerName, Schneidemühl]
  • A. Schneidemühl chosen
    Schneidemühl was a former German town (now Piła in Poland) that historically served as an important regional administrative and railway center.
  • B. Teuschnitz
    Teuschnitz is a small town in northern Bavaria, Germany, known for its rural setting within the Franconian Forest region.
  • C. Dennewitz
    Dennewitz is a village in Brandenburg, Germany, historically notable as the site of a major 1813 battle during the Napoleonic Wars.
  • D. Gadebusch
    Gadebusch is a small historic town in northern Germany known for its medieval architecture and rural surroundings.
  • E. Lommatzsch
    Lommatzsch is a small town in the Free State of Saxony in eastern Germany, known for its agricultural surroundings and historic town 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f33b1c8190bb447788bfd28d51 completed April 14, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd8aca591081908db149ec517a999b completed May 8, 2026, 7:03 a.m.
Created at: April 10, 2026, 1:24 a.m.