Triple

T9382303
Position Surface form Disambiguated ID Type / Status
Subject Roon reforms E225815 entity
Predicate instanceOf P0 FINISHED
Object Prussian reform C24744 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: Prussian reform
Context triple: [Roon reforms, instanceOf, Prussian reform]
  • A. Ottoman reform movement
    The Ottoman reform movement was a series of 19th- and early 20th-century state-led initiatives aimed at modernizing the empire’s military, administration, legal system, and society to strengthen central authority and respond to internal and external pressures.
  • B. Napoleonic policy
    Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
  • C. centralization reform chosen
    Centralization reform is a process of restructuring governance or organizational systems to concentrate decision-making authority, resources, and control within a central body or leadership.
  • D. Byzantine reform movement
    The Byzantine reform movement was a series of religious, administrative, and military initiatives within the Byzantine Empire aimed at strengthening imperial authority, purifying religious practice, and restoring social and economic stability in response to internal decay and external threats.
  • E. Bourbon reform
    The Bourbon Reform was a series of 18th-century administrative, economic, and political changes implemented by the Spanish Bourbon monarchy to centralize power, increase efficiency, and boost revenue in Spain and its American colonies.
  • 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_69ca842e9dcc8190a264119e683cfe04 completed March 30, 2026, 2:09 p.m.
Created at: March 30, 2026, 7:44 p.m.