Triple

T5172402
Position Surface form Disambiguated ID Type / Status
Subject Province of Saxony E116715 entity
Predicate instanceOf P0 FINISHED
Object former Prussian province C8620 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: former Prussian province
Context triple: [Province of Saxony, instanceOf, former Prussian province]
  • A. province of Prussia chosen
    A province of Prussia was a major administrative territorial unit within the Kingdom (and later state) of Prussia, serving as a top-level regional division for governance, law, and administration.
  • B. province of Prussia
    A province of Prussia was a major administrative and territorial division within the Kingdom (and later Free State) of Prussia, functioning as a regional unit of government with its own local authorities under the broader Prussian state.
  • C. former Prussian city
    A former Prussian city is an urban settlement that historically belonged to the Kingdom of Prussia or the later Prussian state but now lies within the borders of a different modern nation.
  • D. constituent state of the German Empire
    A constituent state of the German Empire was one of the semi-autonomous kingdoms, grand duchies, duchies, principalities, free Hanseatic cities, or imperial territories that together formed the federal structure of the German Empire from 1871 to 1918.
  • E. state of Germany
    A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:45 p.m.