Triple
T27945471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Bank of Pakistan Act, 1956 |
E700867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Act of Parliament of Pakistan |
C53575
|
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 Pakistan Context triple: [State Bank of Pakistan Act, 1956, instanceOf, Act of Parliament of Pakistan]
-
A.
Pakistani federal ordinance
A Pakistani federal ordinance is a temporary law issued by the President of Pakistan under constitutional authority, typically when Parliament is not in session, and remains in force for a limited period unless approved or replaced by an Act of Parliament.
-
B.
annex to the Constitution of Pakistan
An annex to the Constitution of Pakistan is a supplementary document formally attached to the Constitution that provides additional details, schedules, or provisions supporting and elaborating its main articles.
-
C.
article of the Constitution of Pakistan
An article of the Constitution of Pakistan is a distinct, numbered provision that defines specific rights, powers, structures, or procedures forming part of the country’s supreme legal framework.
-
D.
Act of Parliament of India
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 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.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 7:21 p.m.