Triple
T33820208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Norodom I |
E866807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Norodom 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: member of the Norodom dynasty Context triple: [King Norodom I, instanceOf, member of the Norodom dynasty]
-
A.
member of Thai royal family
A member of the Thai royal family is an individual who belongs by birth or marriage to the monarchy of Thailand, holding a recognized royal title and status under Thai royal and constitutional traditions.
-
B.
Cambodian royal dynasty
chosen
A Cambodian royal dynasty is a hereditary ruling family that has governed Cambodia over successive generations, shaping the nation’s political authority, cultural identity, and historical continuity.
-
C.
member of the Lý dynasty
A member of the Lý dynasty is an individual belonging to the royal family or ruling elite of the Vietnamese Lý dynasty, which governed Đại Việt from 1009 to 1225.
-
D.
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.
-
E.
Sailendra dynasty member
A Sailendra dynasty member is an individual belonging to the influential Buddhist ruling family that dominated parts of Java and Sumatra in Southeast Asia between the 8th and 9th centuries, known for monumental architecture like Borobudur and extensive maritime trade.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.