Triple
T13654613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocket Docket |
E326824
|
entity |
| Predicate | impactOnPlaintiffs |
P56117
|
FINISHED |
| Object | faster potential relief |
—
|
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: faster potential relief | Statement: [Rocket Docket, impactOnPlaintiffs, faster potential relief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnPlaintiffs Context triple: [Rocket Docket, impactOnPlaintiffs, faster potential relief]
-
A.
impactOnLaw
Indicates the effect or influence that one entity, event, or action has on laws, legal rules, or the legal system.
-
B.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
impactOnCaseFlow
Indicates how an event, action, or decision affects the progression, timing, or movement of cases through a process or system.
-
E.
affectedPeople
chosen
Indicates the people who are impacted or influenced by a particular event, action, or condition.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60ace048190a4b92310ba272bd1 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.