Triple
T2838193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 3 May 1791 |
E62401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Lithuanian Commonwealth 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: Polish–Lithuanian Commonwealth law Context triple: [Constitution of 3 May 1791, instanceOf, Polish–Lithuanian Commonwealth 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.
civil law tradition
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
-
C.
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.
-
D.
medieval legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
-
E.
voivodeship of Poland
A voivodeship of Poland is a top-level administrative region, similar to a province, governed by both elected regional authorities and a centrally appointed governor.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
Created at: March 6, 2026, 10:01 p.m.