Triple
T22406036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lex Frisionum |
E553882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Germanic law |
C34868
|
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: Germanic law Context triple: [Lex Frisionum, instanceOf, Germanic law]
-
A.
medieval law
Medieval law is the body of legal customs, codes, and practices that governed social, economic, and political life in Europe during the Middle Ages, blending local traditions, feudal obligations, royal decrees, and canon (church) law.
-
B.
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.
-
C.
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.
-
D.
barbarian law code
chosen
A barbarian law code is a written compilation of legal customs and rules created by early medieval Germanic or other so‑called “barbarian” peoples, often blending tribal traditions with Roman legal influences.
-
E.
Sardinian legal code
A Sardinian legal code is a structured body of laws and regulations historically or currently governing social, economic, and political life in Sardinia, reflecting its unique cultural, linguistic, and institutional traditions.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.