Triple
T30949010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa M. Nowak |
E788480
|
entity |
| Predicate | criminalCaseOutcome |
P2931
|
FINISHED |
| Object | plea agreement |
—
|
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: plea agreement | Statement: [Lisa M. Nowak, criminalCaseOutcome, plea agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalCaseOutcome Context triple: [Lisa M. Nowak, criminalCaseOutcome, plea agreement]
-
A.
resultOfAccusation
Indicates that one entity is the outcome, consequence, or product of an accusation made by another entity.
-
B.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
C.
legalCaseOutcomeAssociatedWith
Indicates that a particular legal case outcome is connected or linked to a specific related entity, such as a case, party, or legal proceeding.
-
D.
courtReported
Indicates that a court’s decision, proceedings, or judgment have been formally documented and made publicly available in a report or record.
-
E.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.