Triple
T1418039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Hubertusburg |
E31963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 18th-century treaty |
C566
|
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: 18th-century treaty Context triple: [Treaty of Hubertusburg, instanceOf, 18th-century treaty]
-
A.
18th-century organization
An 18th-century organization is a formally or informally structured group of individuals operating during the 1700s to pursue political, economic, social, religious, or intellectual objectives within the historical context of early modern society.
-
B.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
C.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
E.
18th-century ruler
An 18th-century ruler is a sovereign or head of state who governed a territory during the 1700s, navigating the era’s shifting political, economic, and intellectual currents such as absolutism, colonial expansion, and Enlightenment thought.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.