Triple
T8432154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Assyrian commercial law |
E199138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Near Eastern law |
C3214
|
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: ancient Near Eastern law Context triple: [Old Assyrian commercial law, instanceOf, ancient Near Eastern law]
-
A.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
B.
ancient law school
An ancient law school is an educational institution in antiquity where students studied legal codes, rhetoric, and judicial practice under the guidance of learned jurists to prepare for roles in governance and dispute resolution.
-
C.
codification of private law
Codification of private law is the systematic collection and organization of rules governing relationships between private individuals and entities into a coherent, comprehensive legal code.
-
D.
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.
-
E.
system of laws
chosen
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:07 p.m.