Triple

T10611692
Position Surface form Disambiguated ID Type / Status
Subject King Thibaw Min E276022 entity
Predicate instanceOf P0 FINISHED
Object King of Burma C25834 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 Burma
Context triple: [King Thibaw Min, instanceOf, King of Burma]
  • A. Burmese monarchy chosen
    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
    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. Pala emperor
    A Pala emperor is a sovereign ruler of the Pala dynasty who governed large parts of the Indian subcontinent, particularly Bengal and Bihar, during the early medieval period, overseeing political administration, military campaigns, and patronage of Buddhism and culture.
  • D. King of Thailand
    The King of Thailand is the constitutional monarch and head of state of the Kingdom of Thailand, serving as a unifying national figure with cultural, symbolic, and limited political roles under the Thai constitution.
  • E. King of Afghanistan
    The King of Afghanistan was the hereditary monarch and head of state of Afghanistan, traditionally responsible for overseeing governance, foreign relations, and the unification of the country's diverse ethnic and tribal groups until the monarchy's abolition in 1973.
  • 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_69d6aaf948d88190806cc3a8c47a3fb2 completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 7:33 p.m.