Triple
T873357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Powers (Defence) Act 1939 |
E18862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency legislation |
C5555
|
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: emergency legislation Context triple: [Emergency Powers (Defence) Act 1939, instanceOf, emergency legislation]
-
A.
executive order
An executive order is a formal directive issued by a head of the executive branch, such as a president or governor, that manages operations of the government and has the force of law within the scope of existing statutory or constitutional authority.
-
B.
abolitionist legislation
Abolitionist legislation comprises laws and legal measures designed to dismantle systems of slavery, forced labor, or other oppressive institutions and to secure freedom and rights for formerly subjugated people.
-
C.
foreign aid legislation
Foreign aid legislation comprises the laws and policies enacted by a government to authorize, regulate, and oversee the provision of financial, technical, or humanitarian assistance to other countries or international organizations.
-
D.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
-
E.
legislative procedure
Legislative procedure is the formal set of rules and steps through which a legislative body introduces, debates, amends, and decides on proposed laws and resolutions.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.