Triple
T30671178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myinsaing Kingdom |
E780796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Burmese polity |
C25646
|
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: Burmese polity Context triple: [Myinsaing Kingdom, instanceOf, Burmese polity]
-
A.
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.
-
B.
Burmese dynasty
chosen
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.
-
C.
Sinhalese polity
Sinhalese polity refers to the historical and contemporary systems of political organization, governance, and authority exercised by the Sinhalese people in Sri Lanka, shaped by Buddhist kingship, regional kingdoms, colonial rule, and modern state structures.
-
D.
Balinese polity
A Balinese polity is a traditional socio-political entity in Bali characterized by a hierarchical kingship, ritual authority, and complex relationships between royal courts, villages, and religious institutions.
-
E.
Siamese state
A Siamese state is a quantum state composed of two or more subsystems that are structurally identical and correlated in a way that enables comparative or joint processing, often used in tasks like state discrimination or metric learning.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:32 p.m.