Triple
T15030523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victim Compensation Formula Grants |
E378330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crime victim compensation program |
C34668
|
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: crime victim compensation program Context triple: [Victim Compensation Formula Grants, instanceOf, crime victim compensation program]
-
A.
crime victim
A crime victim is an individual who has suffered physical, emotional, or financial harm as a direct result of a criminal act.
-
B.
crime bill
A crime bill is a legislative proposal or enacted law that defines criminal offenses, prescribes penalties, and establishes policies or resources for preventing, investigating, and prosecuting crime.
-
C.
community-based prosecution program
A community-based prosecution program is a collaborative criminal justice approach in which prosecutors work directly within neighborhoods to prevent crime, address local concerns, and build trust through ongoing engagement with community members and organizations.
-
D.
witness protection program
A witness protection program is a government-run system that safeguards threatened witnesses and their families by providing security, relocation, and new identities in exchange for their cooperation in legal proceedings.
-
E.
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.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:59 a.m.