Triple
T34060473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arikesari I |
E873479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SouthIndianRuler |
C48972
|
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: SouthIndianRuler Context triple: [Arikesari I, instanceOf, SouthIndianRuler]
-
A.
ancient Indian ruler
An ancient Indian ruler is a sovereign who governed a region of the Indian subcontinent in antiquity, exercising political, military, and often religious authority over their domain.
-
B.
Chola king
A Chola king is a sovereign ruler of the medieval South Indian Chola dynasty, responsible for governing the kingdom, leading military campaigns, patronizing art and religion, and overseeing administration and trade.
-
C.
Chola emperor
A Chola emperor is the sovereign ruler of the medieval South Indian Chola dynasty, responsible for governing its territories, leading military campaigns, overseeing administration, and patronizing religion, art, and culture.
-
D.
ancient Indian monarch
An ancient Indian monarch is a sovereign ruler of a historical Indian kingdom or empire, wielding political, military, and religious authority over their realm and subjects.
-
E.
medieval Indian ruler
chosen
A medieval Indian ruler is a sovereign who governed a region of the Indian subcontinent between roughly the 8th and 16th centuries, exercising political, military, and cultural authority within a dynastic or imperial framework.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.