Triple
T28808317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Language (Special Provisions) Act |
E727440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Act of Parliament of Sri Lanka |
C54970
|
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: Act of Parliament of Sri Lanka Context triple: [Tamil Language (Special Provisions) Act, instanceOf, Act of Parliament of Sri Lanka]
-
A.
Act of Parliament of Singapore
An Act of Parliament of Singapore is a written law formally enacted by the Singapore Parliament, receiving Presidential assent and forming part of the nation’s primary legislation.
-
B.
Act of Parliament of New Zealand
An Act of Parliament of New Zealand is a law formally enacted by the New Zealand Parliament that establishes, amends, or repeals legal rules within the country’s jurisdiction.
-
C.
Act of the Imperial Legislative Council
An Act of the Imperial Legislative Council is a formal law or statute enacted by the British colonial legislative body in India, possessing binding legal authority within its jurisdiction.
-
D.
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.
-
E.
Sri Lankan chronicle
A Sri Lankan chronicle is a historical narrative text, often composed in Pali or Sinhala, that records the island’s political, religious, and cultural history, typically from a Buddhist monastic perspective.
- 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.