Triple
T23112351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Public Prosecutors Office |
E576352
|
entity |
| Predicate | mayAppeal |
P10643
|
FINISHED |
| Object | court decisions in criminal cases |
—
|
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: court decisions in criminal cases | Statement: [District Public Prosecutors Office, mayAppeal, court decisions in criminal cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAppeal Context triple: [District Public Prosecutors Office, mayAppeal, court decisions in criminal cases]
-
A.
appeal
chosen
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
B.
mayProsecute
Indicates that one party has the legal authority or permission to initiate and conduct prosecution against another party.
-
C.
mayGrantLeaveToAppeal
Indicates that an authority has the power or discretion to allow a party to proceed with an appeal.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
mayFile
Indicates that an entity is permitted or authorized to submit or register a formal document or application.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e100d408190a7349563235640d5 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.