Triple
T34542950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron Swartz’s 2011–2013 JSTOR case |
E886849
|
entity |
| Predicate | defendantPlea |
P1780
|
FINISHED |
| Object | not guilty |
—
|
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: not guilty | Statement: [Aaron Swartz’s 2011–2013 JSTOR case, defendantPlea, not guilty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantPlea Context triple: [Aaron Swartz’s 2011–2013 JSTOR case, defendantPlea, not guilty]
-
A.
dateOfPlea
Indicates the specific calendar date on which a formal plea was entered in a legal proceeding.
-
B.
plea
chosen
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
C.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
D.
pleaTo
Indicates that one entity formally requests or appeals to another entity, often seeking a specific decision, action, or lenient judgment.
-
E.
pleadedGuilty
Indicates that a defendant formally admitted in court that they committed the offense with which they were charged.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 2:02 a.m.