Triple
T22985285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutes of Wiślica |
E571589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish legal code |
C31822
|
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 legal code Context triple: [Statutes of Wiślica, instanceOf, Polish legal code]
-
A.
Prussian law
Prussian law refers to the body of legal principles, statutes, and judicial practices that governed the Kingdom of Prussia, characterized by a strong centralized authority, codification efforts like the Allgemeines Landrecht, and an emphasis on bureaucratic administration and social order.
-
B.
foundational law of the Polish–Lithuanian Commonwealth
A foundational law of the Polish–Lithuanian Commonwealth is a core constitutional act or legal principle that defined the political structure, rights, and governance of the union between Poland and Lithuania.
-
C.
Czech statute
A Czech statute is a formal written law enacted by the Parliament of the Czech Republic that establishes, modifies, or regulates legal rights and obligations within the Czech legal system.
-
D.
Polish historical document
chosen
A Polish historical document is an original or reproduced written, printed, or otherwise recorded source created in or about Poland’s past, providing evidence and context for historical events, people, institutions, or cultural practices.
-
E.
Croatian statute
A Croatian statute is a formal written law enacted by the Croatian Parliament (Sabor) that regulates specific areas of public or private life within the Republic of Croatia’s legal system.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:49 p.m.