Triple
T25175009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undang-Undang Kedah |
E630424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Malay legal 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: traditional Malay legal code Context triple: [Undang-Undang Kedah, instanceOf, traditional Malay legal code]
-
A.
Malacca Sultanate law code
chosen
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.
-
B.
traditional Malay clothing
Traditional Malay clothing encompasses the culturally significant garments such as baju kurung, baju Melayu, and songket, characterized by modest silhouettes, rich textiles, and intricate decorative motifs that reflect Malay heritage and identity.
-
C.
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.
-
D.
Mongol law
Mongol law refers to the legal principles, customary practices, and codified regulations—most notably the Yassa—developed under the Mongol Empire to govern its diverse subjects, maintain military discipline, and ensure social order across vast conquered territories.
-
E.
Philippine legal code
The Philippine legal code is the comprehensive body of laws, statutes, and regulations that govern the rights, duties, and conduct of individuals and institutions within the Republic of the Philippines.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:33 p.m.