Triple
T28808360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandaranaike family |
E727441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sri Lankan political dynasty |
C54971
|
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: Sri Lankan political dynasty Context triple: [Bandaranaike family, instanceOf, Sri Lankan political dynasty]
-
A.
Sinhalese polity
Sinhalese polity refers to the historical and contemporary systems of political organization, governance, and authority exercised by the Sinhalese people in Sri Lanka, shaped by Buddhist kingship, regional kingdoms, colonial rule, and modern state structures.
-
B.
Pakistani political dynasty
A Pakistani political dynasty is a powerful family whose members, across multiple generations, occupy influential political positions and shape national or regional governance, often leveraging inherited status, patronage networks, and party control.
-
C.
Indian political dynasty
An Indian political dynasty is a family-based power structure in which multiple generations of relatives hold significant political offices and influence across parties, regions, or levels of government in India.
-
D.
Sri Lankan monarch
A Sri Lankan monarch is a sovereign ruler of Sri Lanka’s historical kingdoms, holding supreme political and ceremonial authority over the island and its people.
-
E.
Sri Lankan businessperson
A Sri Lankan businessperson is an individual from Sri Lanka engaged in commercial, industrial, or entrepreneurial activities, contributing to the country's economic development through business ventures and corporate leadership.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:30 a.m.