Triple
T31465434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment Relations Authority |
E802709
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | employment dispute resolution body |
C26018
|
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 dispute resolution body Context triple: [Employment Relations Authority, instanceOf, employment dispute resolution body]
-
A.
tax dispute resolution body
A tax dispute resolution body is an independent authority or tribunal that reviews and adjudicates disagreements between taxpayers and tax authorities over assessments, liabilities, or interpretations of tax law.
-
B.
labor relations board
chosen
A labor relations board is a governmental or quasi-judicial body that oversees and enforces laws governing collective bargaining, union representation, and the resolution of labor-management disputes.
-
C.
transnational employee representation body
A transnational employee representation body is an organized group of worker representatives operating across multiple countries within a multinational company to inform, consult, and sometimes negotiate on employees’ collective interests at the cross-border level.
-
D.
labor organization body
A labor organization body is a formal group or institution that represents workers’ collective interests in negotiations, advocacy, and regulation of labor conditions and rights.
-
E.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
- 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.