Triple
T21850000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott Sullivan |
E539477
|
entity |
| Predicate | pleaAgreement |
P611
|
FINISHED |
| Object | cooperation agreement with prosecutors |
—
|
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: cooperation agreement with prosecutors | Statement: [Scott Sullivan, pleaAgreement, cooperation agreement with prosecutors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pleaAgreement Context triple: [Scott Sullivan, pleaAgreement, cooperation agreement with prosecutors]
-
A.
plea
Indicates that a defendant formally states their response (such as guilty, not guilty, or no contest) to criminal charges in a legal proceeding.
-
B.
pleadsWith
Indicates that one entity urgently and emotionally appeals to another, often requesting help, mercy, or a favorable decision.
-
C.
agreement
chosen
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
D.
negotiatedPursuantTo
Indicates that a negotiation occurred in accordance with, or as required by, a specific agreement, rule, provision, or legal/contractual framework.
-
E.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd582ca48190890648fdee2a0c6e |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.