Triple
T31349602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayinnaung |
E799549
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toungoo dynasty ruler |
C29770
|
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: Toungoo dynasty ruler Context triple: [Bayinnaung, instanceOf, Toungoo dynasty ruler]
-
A.
Manghit dynasty ruler
A Manghit dynasty ruler is a sovereign from the Uzbek Manghit family who governed the Emirate of Bukhara, overseeing its political, military, and religious affairs from the mid-18th to early 20th centuries.
-
B.
Burmese monarch
chosen
A Burmese monarch is the sovereign ruler of a historical Burmese kingdom, wielding supreme political, military, and religious authority over the realm and its subjects.
-
C.
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.
-
D.
Ahom ruler
An Ahom ruler is a sovereign of the Ahom kingdom in medieval and early modern Assam, responsible for governance, military leadership, and the preservation of Ahom culture and political authority.
-
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.
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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.