Triple
T9956802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Assyrian Laws |
E195465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian law code |
C5560
|
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: Assyrian law code Context triple: [Middle Assyrian Laws, instanceOf, Assyrian law code]
-
A.
ancient Near Eastern law collection
chosen
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.
Moabite inscription
A Moabite inscription is an ancient text carved in the Moabite language, typically on stone or other durable materials, that records historical, religious, or political information from the Iron Age kingdom of Moab.
-
D.
Proto-Canaanite inscription
A Proto-Canaanite inscription is an early alphabetic text, typically carved on stone or pottery in the Levant during the late second millennium BCE, representing one of the earliest known stages of the Canaanite (and thus later Phoenician and Hebrew) writing system.
-
E.
Sumerian temple hymn
A Sumerian temple hymn is an ancient Mesopotamian poetic composition that praises a specific temple and its deity, celebrating the sacred space’s divine presence, power, and ritual significance.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.