Triple
T28808529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Hammurabi stele |
E727445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient legal monument |
C27632
|
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 legal monument Context triple: [Code of Hammurabi stele, instanceOf, ancient legal monument]
-
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 Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
-
C.
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.
-
D.
ancient structure
chosen
An ancient structure is a man-made construction from antiquity, such as temples, fortifications, or monuments, that reflects the architectural techniques, cultural values, and historical context of its originating civilization.
-
E.
hieroglyphic inscription monument
A hieroglyphic inscription monument is a physical structure, such as a stela, wall, or pillar, bearing carved or painted hieroglyphic texts that record religious, political, historical, or commemorative information.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:30 a.m.