Triple
T14061794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yassa legal code (attributed) |
E338363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary legal code |
C21846
|
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: legendary legal code Context triple: [Yassa legal code (attributed), instanceOf, legendary legal code]
-
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.
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.
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.
system of laws
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.
-
E.
historical legal text
chosen
A historical legal text is a written document from a past era that records laws, legal decisions, or legal reasoning, reflecting the legal norms, institutions, and societal values of its time.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.