Triple
T14311936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJA panel attorney |
E354852
|
entity |
| Predicate | caseScope |
P81213
|
FINISHED |
| Object | federal criminal prosecutions |
—
|
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: federal criminal prosecutions | Statement: [CJA panel attorney, caseScope, federal criminal prosecutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseScope Context triple: [CJA panel attorney, caseScope, federal criminal prosecutions]
-
A.
caseLocation
Indicates the specific place or jurisdiction in which a case or legal matter is situated, filed, or adjudicated.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
caseTypes
chosen
Indicates the types or categories of cases associated with or applicable to an entity or situation.
-
D.
trialScope
Indicates that an action, condition, or rule applies only within the defined boundaries or context of a specific trial or experimental instance.
-
E.
caseOfScottorum
Indicates that something pertains to, is associated with, or is characteristic of the Scots or Scotland.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.