Triple
T18521148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title III – Disputes Between Carriers and Their Employees |
E452585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | labor law provision |
C758
|
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: labor law provision Context triple: [Title III – Disputes Between Carriers and Their Employees, instanceOf, labor law provision]
-
A.
labor law
chosen
Labor law is the body of rules and principles governing the rights, duties, and relationships between employers, employees, and labor organizations in the workplace.
-
B.
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.
-
C.
labor accord
A labor accord is a formal agreement between employers and workers or their unions that sets terms and conditions of employment, such as wages, hours, and workplace rights, to prevent or resolve labor disputes.
-
D.
labor relations board
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.
-
E.
amendment to the Fair Labor Standards Act
An amendment to the Fair Labor Standards Act is a legislative change that modifies, adds to, or clarifies the federal rules governing minimum wage, overtime pay, child labor, and related employment standards in the United States.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.