Triple
T15140448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carta de Logu |
E361669
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sardinian legal code |
C36020
|
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: Sardinian legal code Context triple: [Carta de Logu, instanceOf, Sardinian legal code]
-
A.
Byzantine law code
A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
-
B.
Albanian customary law
Albanian customary law is a traditional, unwritten legal system—most famously embodied in the Kanun—that historically governed social conduct, conflict resolution, and community obligations in Albanian society.
-
C.
barbarian law code
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.
-
D.
late Roman legal codex
A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
-
E.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
- F. None of above. chosen
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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.