Triple
T26993793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toramana |
E679925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Huna ruler |
C52351
|
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: Huna ruler Context triple: [Toramana, instanceOf, Huna ruler]
-
A.
Shunga ruler
A Shunga ruler is a monarch from the Shunga dynasty (c. 185–73 BCE) in ancient India, known for governing a post-Mauryan empire centered in northern and central India and for patronizing Brahmanical traditions and early art.
-
B.
Ryukyuan lord
A Ryukyuan lord was a regional noble of the Ryukyu Kingdom who governed local territories, managed tribute and trade, and served the royal court in a hierarchical feudal system influenced by both Japanese and Chinese cultures.
-
C.
Vakataka king
A Vakataka king is a ruler from the ancient Indian Vakataka dynasty (c. 3rd–5th century CE), known for governing central and southern India and patronizing art, architecture, and literature, including the Ajanta caves.
-
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.
Gond ruler
A Gond ruler is a sovereign or chieftain from the Gond community who governs a territory, oversees administration and justice, and upholds the cultural and political traditions of the Gond people.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:53 a.m.