Triple
T15169945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Appeals unit |
E362458
|
entity |
| Predicate | legalProcessStage |
P113457
|
FINISHED |
| Object | appeals |
—
|
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: appeals | Statement: [Criminal Appeals unit, legalProcessStage, appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalProcessStage Context triple: [Criminal Appeals unit, legalProcessStage, appeals]
-
A.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
B.
disputeSettlementStage
chosen
Indicates the specific phase or step reached in the process of resolving a dispute.
-
C.
relatedLegalProcess
Indicates that there is an associated legal proceeding or action that is connected to, arises from, or is otherwise relevant to the referenced entity or event.
-
D.
judicialStatus
Indicates the legal or court-related condition or standing of an entity within a judicial process (e.g., pending, decided, appealed).
-
E.
courtStatus
Indicates the current legal or procedural state of a case or matter within a court system.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064ec56481909f11fa6e5686f076 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.