Triple
T38610060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain Timber Co. v. Washington |
E934452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | workers’ compensation case |
C38123
|
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: workers’ compensation case Context triple: [Mountain Timber Co. v. Washington, instanceOf, workers’ compensation case]
-
A.
workers’ compensation court
A workers’ compensation court is a specialized judicial body that resolves disputes between employees, employers, and insurers over benefits and claims arising from work-related injuries and occupational diseases.
-
B.
labor law–related case
chosen
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.
workers' accident insurance institute
A workers' accident insurance institute is an organization that provides mandatory insurance coverage and related services to protect employees and employers against the financial consequences of work-related accidents and occupational diseases.
-
D.
disability law case
A disability law case is a legal dispute in which an individual or group alleges discrimination, denial of reasonable accommodation, or violation of rights based on disability under relevant statutes and regulations.
-
E.
negligence case
A negligence case is a legal action in which a plaintiff seeks compensation by claiming the defendant failed to exercise reasonable care, causing foreseeable harm or injury.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.