Triple
T12445401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protection of Lawful Commerce in Arms Act |
E297384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tort liability immunity law |
C31468
|
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: tort liability immunity law Context triple: [Protection of Lawful Commerce in Arms Act, instanceOf, tort liability immunity law]
-
A.
liability and compensation protocol
A liability and compensation protocol defines the rules, processes, and mechanisms by which responsibility for harm or loss is assigned and appropriate restitution or payment is calculated, allocated, and delivered among involved parties.
-
B.
insurance defense law firm
An insurance defense law firm is a legal practice that represents insurance companies and their insureds in defending against claims and lawsuits, focusing on minimizing liability and financial exposure.
-
C.
legal jurisdiction
A legal jurisdiction is a defined geographic area or subject-matter domain within which a particular court or governmental authority has the power to create, interpret, and enforce laws.
-
D.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
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. 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_69d6ada166c48190b902972cd2408fa3 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.