Triple
T29376395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undang of Rembau |
E745009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Malay customary office |
C51211
|
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: Malay customary office Context triple: [Undang of Rembau, instanceOf, Malay customary office]
-
A.
Malay customary law
Malay customary law is the body of traditional norms, practices, and unwritten rules that historically governed social relations, property, and dispute resolution among Malay communities, often coexisting with Islamic law and colonial legal systems.
-
B.
customary office
chosen
A customary office is a position of authority or responsibility that exists and is recognized primarily through long-standing tradition and practice rather than formal legal or written establishment.
-
C.
Karbi customary institution
Karbi customary institution refers to the traditional socio-political and judicial structures of the Karbi community that regulate social order, resolve disputes, and preserve cultural norms through customary laws and practices.
-
D.
state office in Malaysia
A state office in Malaysia is a governmental administrative entity responsible for implementing federal and state policies, delivering public services, and managing local governance within a specific Malaysian state.
-
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.
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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:31 p.m.