Triple
T25864712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhodian Sea Law |
E651579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient maritime law code |
C50832
|
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 maritime law code Context triple: [Rhodian Sea Law, instanceOf, ancient maritime law code]
-
A.
Sardinian legal code
A Sardinian legal code is a structured body of laws and regulations historically or currently governing social, economic, and political life in Sardinia, reflecting its unique cultural, linguistic, and institutional traditions.
-
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 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.
-
D.
dynastic legal code
A dynastic legal code is a formalized set of laws and regulations established and enforced by a ruling dynasty to govern its subjects, institutions, and social order.
-
E.
Malacca Sultanate law code
The Malacca Sultanate law code is a historical legal framework that governed political authority, trade, social conduct, and Islamic practices in the Malacca Sultanate, serving as a foundational reference for later Malay legal traditions.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:06 a.m.