Triple
T8561119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disaster Management Act, 2005 |
E202692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Act of Parliament |
C7063
|
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: Indian Act of Parliament Context triple: [Disaster Management Act, 2005, instanceOf, Indian Act of Parliament]
-
A.
Act of Parliament of Canada
An Act of Parliament of Canada is a law formally enacted by the Parliament of Canada, consisting of the House of Commons, the Senate, and the Crown, that establishes or amends legal rules applicable within Canada.
-
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 Parliament of Australia
An Act of Parliament of Australia is a law formally enacted by the Australian Parliament, comprising the House of Representatives and the Senate, that has received Royal Assent and is binding within the Australian legal system.
-
D.
Act of Parliament of India
chosen
An Act of Parliament of India is a formal written law enacted by the Indian Parliament through its legislative process, which becomes legally binding upon receiving presidential assent and publication.
-
E.
Act of Parliament of the United Kingdom
An Act of Parliament of the United Kingdom is a formal law enacted by the UK Parliament, comprising the House of Commons, the House of Lords, and the monarch, which has legal force throughout its applicable jurisdictions.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:20 p.m.