Triple
T30819466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanunname |
E784876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman legal code |
C24118
|
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: Ottoman legal code Context triple: [Kanunname, instanceOf, Ottoman legal code]
-
A.
Ottoman law
chosen
Ottoman law refers to the complex legal system of the Ottoman Empire, combining Islamic (Sharia) principles, sultanic decrees (Kanun), and customary practices to govern its diverse populations and administrative affairs.
-
B.
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.
-
C.
Malacca Sultanate law code
The Malacca Sultanate law code is a historical legal framework that governed political authority, trade, social conduct, and Islamic practices in the Malacca Sultanate, serving as a foundational reference for later Malay legal traditions.
-
D.
dynastic legal code
A dynastic legal code is a formalized set of laws and regulations established and enforced by a ruling dynasty to govern its subjects, institutions, and social order.
-
E.
Mughal-era legal code
A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:44 p.m.