Triple

T29783056
Position Surface form Disambiguated ID Type / Status
Subject Freiberg district E756177 entity
Predicate instanceOf P0 FINISHED
Object administrative district of Saxony C11251 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: administrative district of Saxony
Context triple: [Freiberg district, instanceOf, administrative district of Saxony]
  • A. district of Saxony chosen
    A district of Saxony is an administrative subdivision within the federal state of Saxony in Germany, responsible for local governance, public services, and regional planning across multiple municipalities.
  • B. administrative district of East Germany
    An administrative district of East Germany was a mid-level territorial unit (Bezirk) established by the German Democratic Republic to organize regional governance, planning, and administration between the central government and local municipalities.
  • C. district of Leipzig
    A district of Leipzig is an administrative subdivision of the city that encompasses specific neighborhoods, local infrastructure, and community services within defined geographic boundaries.
  • D. administrative region of Bavaria
    An administrative region of Bavaria is a territorial subdivision within the German state of Bavaria that serves as an intermediate level of government, coordinating regional administration, planning, and public services across its constituent districts and municipalities.
  • E. district of Zwickau
    The district of Zwickau is an administrative region in the Free State of Saxony, Germany, encompassing the city of Zwickau and surrounding towns and rural areas, known for its industrial heritage and cultural history.
  • F. None of above.

Provenance (1 batch)

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_69f22451fb748190bbdbab401280affb completed April 29, 2026, 3:31 p.m.
Created at: April 29, 2026, 5:06 p.m.