Triple
T17588116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosecutor General of Poland |
E428376
|
entity |
| Predicate | maySubmit |
P104189
|
FINISHED |
| Object | extraordinary appeals in specified 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: extraordinary appeals in specified cases | Statement: [Prosecutor General of Poland, maySubmit, extraordinary appeals in specified cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySubmit Context triple: [Prosecutor General of Poland, maySubmit, extraordinary appeals in specified cases]
-
A.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
B.
mayPass
Indicates that one entity is permitted or authorized to move through, cross, or gain access to another entity or location.
-
C.
mayApply
chosen
Indicates that an entity is permitted or eligible to submit or use something (such as a rule, action, or resource) under certain conditions.
-
D.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e50a80819098920d9190c30225 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.