Triple
T10653376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Am Prepared to Die |
E251027
|
entity |
| Predicate | legalChargeContext |
P1779
|
FINISHED |
| Object | sabotage |
—
|
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: sabotage | Statement: [I Am Prepared to Die, legalChargeContext, sabotage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalChargeContext Context triple: [I Am Prepared to Die, legalChargeContext, sabotage]
-
A.
legalCharge
chosen
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
-
B.
legalContext
Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
-
C.
chargeJurisdiction
Indicates that an authority has the legal power or jurisdiction to bring or pursue charges in relation to a particular case or entity.
-
D.
legalCaseAlongside
Indicates that two or more legal cases are proceeding in parallel or in coordination, such that they are related or handled together in some aspect of the legal process.
-
E.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
- F. None of above.
Provenance (3 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff85674819099bf40c9f4fede15 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.