Triple
T16367436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assizes of Jerusalem |
E397472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of feudal law |
C9503
|
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: source of feudal law Context triple: [Assizes of Jerusalem, instanceOf, source of feudal 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.
source of Byzantine law
A source of Byzantine law is any authoritative origin—such as imperial legislation, ecclesiastical canons, juristic writings, or customary practices—from which the legal norms of the Byzantine Empire were derived and recognized.
-
C.
medieval legislation
chosen
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.
-
D.
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.
-
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.
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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:08 a.m.