Triple
T16722527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaffna Kingdom |
E406385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tamil monarchy |
C20889
|
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: Tamil monarchy Context triple: [Jaffna Kingdom, instanceOf, Tamil monarchy]
-
A.
Tamil dynasty
A Tamil dynasty is a ruling lineage originating from the Tamil-speaking regions of South India and Sri Lanka, characterized by its political authority, cultural patronage, and influence over Tamil society and history.
-
B.
South Indian dynasty
A South Indian dynasty is a long-standing ruling lineage or family that governed regions of southern India, shaping its political history, culture, religion, and art over successive generations.
-
C.
South Indian royal dynasty
chosen
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
-
D.
Bengal dynasty
The Bengal dynasty refers to the succession of ruling families and political powers that governed the Bengal region (in present-day Bangladesh and eastern India) across various historical periods, shaping its cultural, economic, and political development.
-
E.
Cham polity
Cham polity refers to the historical political entities and state structures formed by the Cham people in mainland Southeast Asia, particularly in what is now central and southern Vietnam, characterized by maritime trade, Hindu-Buddhist cultural influences, and shifting regional power dynamics.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.