Triple
T29384440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | appellate courts of Ukraine |
E745213
|
entity |
| Predicate | mayUphold |
P166702
|
FINISHED |
| Object | decision of lower court |
—
|
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: decision of lower court | Statement: [appellate courts of Ukraine, mayUphold, decision of lower court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayUphold Context triple: [appellate courts of Ukraine, mayUphold, decision of lower court]
-
A.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
B.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
C.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
D.
mayApprove
Indicates that an entity has the authority or permission to approve another entity or action, but is not required to do so.
-
E.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
- F. None of above. chosen
Provenance (4 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d0c45c8190ac5b67a0e89e8aae |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:37 p.m.