Triple
T17451148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Norodom |
E424915
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cambodian royal dynasty |
C39252
|
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: Cambodian royal dynasty Context triple: [House of Norodom, instanceOf, Cambodian royal dynasty]
-
A.
Cambodian prince
A Cambodian prince is a male member of Cambodia’s royal family who holds hereditary noble status and may perform ceremonial, cultural, or political roles within the kingdom’s constitutional monarchy.
-
B.
Burmese monarchy
The Burmese monarchy was the traditional hereditary system of kingship that ruled over Burma (Myanmar) for centuries, embodying both political authority and religious legitimacy until its abolition under British colonial rule.
-
C.
Malay royal dynasty
A Malay royal dynasty is a hereditary ruling family of Malay origin that traditionally governs a Malay state or sultanate, embodying political authority, cultural leadership, and continuity of lineage.
-
D.
Minangkabau royal dynasty
The Minangkabau royal dynasty is the traditional ruling lineage of the Minangkabau people of West Sumatra, Indonesia, historically governing through a matrilineal adat system that blended indigenous customs with Islamic influences.
-
E.
Burmese dynasty
A Burmese dynasty is a succession of rulers from the same family or lineage that governed regions of present-day Myanmar, shaping its political, cultural, and religious history over a defined historical period.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.