Triple
T19646690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | awarded to Archer-Shee family |
E471691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal compensation award |
C3028
|
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: legal compensation award Context triple: [awarded to Archer-Shee family, instanceOf, legal compensation award]
-
A.
legal settlement
chosen
A legal settlement is an agreement between disputing parties to resolve a legal claim or lawsuit, typically involving negotiated terms such as payment or actions, without proceeding to a final court judgment.
-
B.
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.
-
C.
crime victim compensation program
A crime victim compensation program is a government-administered system that provides financial assistance and support services to eligible individuals who have suffered physical, emotional, or financial harm as a result of criminal activity.
-
D.
legal aftermath
Legal aftermath is the period following a legal decision or event in which consequences such as enforcement, appeals, compliance measures, and broader social or institutional impacts unfold.
-
E.
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.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:44 p.m.