Triple
T5289298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian System of Patient Injury Compensation |
E119702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | no-fault patient injury compensation scheme |
C18322
|
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: no-fault patient injury compensation scheme Context triple: [Norwegian System of Patient Injury Compensation, instanceOf, no-fault patient injury compensation scheme]
-
A.
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.
-
B.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
C.
product liability case
A product liability case is a legal action in which a consumer seeks compensation for injuries or damages caused by a defective or unsafe product, alleging fault by the manufacturer, distributor, or seller.
-
D.
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.
-
E.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
- F. None of above. chosen
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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:52 p.m.