Triple
T1334015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Body of Civil Law |
E28706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine law code |
C6479
|
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: Byzantine law code Context triple: [Body of Civil Law, instanceOf, Byzantine law code]
-
A.
ecclesiastical law code
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
-
B.
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.
-
C.
Byzantine city
A Byzantine city is an urban center of the Eastern Roman (Byzantine) Empire characterized by fortified walls, Christian religious institutions, administrative and commercial hubs, and a blend of Greco-Roman and Eastern cultural influences.
-
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.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.