Triple
T13915885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yassa |
E334619
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol law |
C34366
|
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: Mongol law Context triple: [Yassa, instanceOf, Mongol law]
-
A.
Ottoman law
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.
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.
-
C.
Chinese legal code
A Chinese legal code is a systematically organized collection of laws and regulations that defines legal norms, rights, obligations, and penalties within a Chinese jurisdiction.
-
D.
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.
-
E.
Russian imperial law
Russian imperial law was the evolving body of statutes, decrees, and legal principles that governed the Russian Empire from the early tsarist period through 1917, reflecting autocratic authority, codified reforms, and complex interactions among imperial, regional, and customary norms.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.