Triple
T16287910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Locrian Epizephyrian law code |
E395437
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Greek law code |
C32962
|
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 Greek law code Context triple: [Locrian Epizephyrian law code, instanceOf, ancient Greek law code]
-
A.
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.
-
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.
ancient Greek treaty
An ancient Greek treaty is a formal, often inscribed agreement between city-states or powers that establishes terms of peace, alliance, or mutual obligations under the sanction of the gods.
-
D.
Athenian legal proceeding
An Athenian legal proceeding is a public, citizen-driven trial in classical Athens where litigants present their own cases before a large jury of fellow citizens who decide verdict and penalty without professional judges or lawyers.
-
E.
Greek law
chosen
Greek law is the body of legal principles, institutions, and practices that originated in ancient Greek city-states and evolved through Hellenistic, Roman, Byzantine, and modern periods to govern social, political, and economic life in Greek 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.