Triple
T31465533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment Relations Act 2000 |
E802711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | employment law statute |
C53925
|
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: employment law statute Context triple: [Employment Relations Act 2000, instanceOf, employment law statute]
-
A.
employment law instrument
chosen
An employment law instrument is a formal legal source—such as a statute, regulation, contract, or collective agreement—that establishes, governs, or modifies the rights and obligations arising from an employment relationship.
-
B.
labor law
Labor law is the body of rules and principles governing the rights, duties, and relationships between employers, employees, and labor organizations in the workplace.
-
C.
employee benefits law
Employee benefits law governs the creation, administration, and regulation of employer-sponsored benefit plans—such as health insurance, retirement, and disability programs—ensuring compliance with legal standards and protection of employees’ rights.
-
D.
labor law–related case
A labor law–related case is a legal dispute or judicial proceeding that centers on the interpretation, application, or enforcement of laws and regulations governing employment relationships, workers’ rights, and workplace conditions.
-
E.
veterans employment statute
A veterans employment statute is a legal provision that grants hiring preferences, protections, or benefits to military veterans in public or private employment to support their transition to and retention in civilian jobs.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:22 p.m.