Triple
T10800103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois criminal law |
E254814
|
entity |
| Predicate | recognizesDefense |
P95536
|
FINISHED |
| Object | self-defense under Illinois law |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: self-defense under Illinois law | Statement: [Illinois criminal law, recognizesDefense, self-defense under Illinois law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesDefense Context triple: [Illinois criminal law, recognizesDefense, self-defense under Illinois law]
-
A.
defensiveCapability
Indicates the ability or capacity of an entity to protect itself or others against threats, attacks, or harm.
-
B.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
C.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending another entity.
-
D.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
E.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
- F. None of above. chosen
Provenance (4 batches)
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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733366c408190bfd3b57be5ef2440 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:18 p.m.