Triple
T27896700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramkhamhaeng of Sukhothai |
E705512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | King of Sukhothai |
C53520
|
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: King of Sukhothai Context triple: [Ramkhamhaeng of Sukhothai, instanceOf, King of Sukhothai]
-
A.
King of Ayutthaya
The King of Ayutthaya was the supreme monarch of the Ayutthaya Kingdom, ruling as both political and religious leader over a powerful Siamese state in present-day Thailand from the 14th to the 18th century.
-
B.
Khmer king
A Khmer king is the sovereign ruler of the historical Khmer Empire or modern Cambodia, embodying political authority, religious legitimacy, and cultural leadership over the Khmer people.
-
C.
King of Laos
The King of Laos was the hereditary monarch and head of state of the Kingdom of Laos, symbolizing national unity and traditional authority until the monarchy’s abolition in 1975.
-
D.
King of Lanna
The King of Lanna is the sovereign ruler of the historical Lanna Kingdom in northern Thailand, responsible for governing its territories, upholding its cultural and religious traditions, and maintaining political and military power.
-
E.
Ahom king
An Ahom king was the hereditary monarch of the Ahom dynasty in Assam, who ruled the kingdom, led military campaigns, oversaw administration, and patronized religion and culture from the 13th to the early 19th century.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 6:39 p.m.