Triple
T36501919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langdarma |
E899353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tibetan king |
C64059
|
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: Tibetan king Context triple: [Langdarma, instanceOf, Tibetan king]
-
A.
King of Nepal
The King of Nepal was the hereditary monarch and head of state of the Kingdom of Nepal, traditionally regarded as a unifying national figure and symbol of the country's sovereignty until the monarchy's abolition in 2008.
-
B.
Chogyal of Sikkim
The Chogyal of Sikkim was the hereditary Buddhist monarch of the former Kingdom of Sikkim, serving as both its temporal ruler and spiritual leader until the monarchy’s abolition in 1975.
-
C.
monarch of Gorkha
The monarch of Gorkha is the hereditary sovereign ruler of the historic Gorkha Kingdom in present-day Nepal, holding supreme political and symbolic authority over its territories and people.
-
D.
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.
-
E.
Shakya clan leader
A Shakya clan leader is the hereditary or elected head of the ancient Shakya community, responsible for governance, protection, and the preservation of the clan’s social, cultural, and religious traditions.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.