Triple
T4815449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jervis Bay Territory Acceptance Act 1915 |
E107176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Commonwealth of Australia law |
C13658
|
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: Commonwealth of Australia law Context triple: [Jervis Bay Territory Acceptance Act 1915, instanceOf, Commonwealth of Australia law]
-
A.
Act of Parliament of Australia
chosen
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.
-
B.
British colonial law
British colonial law refers to the legal systems, statutes, and judicial practices imposed by Britain on its colonies, designed to maintain imperial control while selectively incorporating or reshaping local customs and institutions.
-
C.
Welsh law
Welsh law is the distinct body of legal rules, principles, and institutions applicable in Wales, shaped by devolution, historical Welsh legal traditions, and its integration within the broader legal system of England and Wales.
-
D.
system of laws
A system of laws is an organized and coherent set of rules and principles established by an authority to regulate behavior, resolve disputes, and maintain order within a society.
-
E.
state of Australia
A state of Australia is a primary political and administrative division of the country, each with its own government, parliament, and constitution operating under the federal system of the Commonwealth of Australia.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.