Triple
T1008316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil Constitution of the Clergy |
E21763
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French revolutionary law |
C3214
|
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: French revolutionary law Context triple: [Civil Constitution of the Clergy, instanceOf, French revolutionary law]
-
A.
Russian imperial law
Russian imperial law was the evolving body of statutes, decrees, and legal principles that governed the Russian Empire from the early tsarist period through 1917, reflecting autocratic authority, codified reforms, and complex interactions among imperial, regional, and customary norms.
-
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.
French jurist
A French jurist is a legal scholar or practitioner from France who specializes in interpreting, analyzing, and applying French law within its civil law tradition.
-
D.
system of laws
chosen
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
-
E.
revolutionary congress
A revolutionary congress is a formal assembly of representatives convened to lead, coordinate, and legitimize a political or social revolution, often drafting new governing frameworks and strategies for transformative change.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.