Triple
T529799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Peru |
E10999
|
entity |
| Predicate | typeOfAppeals |
P15240
|
FINISHED |
| Object | cassation 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: cassation appeals | Statement: [Supreme Court of Peru, typeOfAppeals, cassation appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAppeals Context triple: [Supreme Court of Peru, typeOfAppeals, cassation appeals]
-
A.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
B.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
C.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
D.
appealsGoTo
Indicates that appeals arising from a decision or judgment are directed to and handled by a specified higher authority or court.
-
E.
alsoAppealsTo
Indicates that something attracts, interests, or is pleasing to an additional person, group, or audience beyond the primary one.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d4984c8190ac372171b16bb5e4 |
completed | Feb. 28, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.