Triple
T36059043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Cassation of Morocco |
E1043024
|
entity |
| Predicate | mayRemandTo |
P12548
|
FINISHED |
| Object | lower courts |
—
|
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: lower courts | Statement: [Court of Cassation of Morocco, mayRemandTo, lower courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRemandTo Context triple: [Court of Cassation of Morocco, mayRemandTo, lower courts]
-
A.
canRemand
chosen
Indicates that an authority (such as a court or decision-maker) has the power to send a case or matter back to a lower body or earlier stage for further action or reconsideration.
-
B.
mayGrantLeaveToAppeal
Indicates that an authority has the power or discretion to allow a party to proceed with an appeal.
-
C.
mayProsecute
Indicates that one party has the legal authority or permission to initiate and conduct prosecution against another party.
-
D.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
E.
mayReverse
Indicates that an action, process, or state can be undone or returned to a previous condition.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.