Triple
T8256405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehcir Law |
E193080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ottoman law |
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 law Context triple: [Tehcir Law, instanceOf, Ottoman law]
-
A.
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.
-
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.
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.
-
D.
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.
-
E.
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.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:49 p.m.