Triple
T6902703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undang-Undang Melaka |
E159531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malacca Sultanate law code |
C21847
|
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: Malacca Sultanate law code Context triple: [Undang-Undang Melaka, instanceOf, Malacca Sultanate law code]
-
A.
Srivijaya inscription
A Srivijaya inscription is an ancient written record, typically in Old Malay or Sanskrit, produced by the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
B.
Srivijayan inscription
A Srivijayan inscription is an ancient written record, typically carved in stone or metal, produced under the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
C.
Malay kingdom
A Malay kingdom is a traditional political entity in the Malay world, typically ruled by a sultan or raja, characterized by Malay culture, Islam, and control over regional trade networks.
-
D.
Mughal-era legal code
A Mughal-era legal code is a structured body of laws, regulations, and judicial principles developed under the Mughal Empire that governed civil, criminal, fiscal, and religious matters by blending Islamic jurisprudence with local customs and imperial decrees.
-
E.
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.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:25 p.m.