Triple
T32480003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribunales de Juicio Oral en lo Penal |
E830081
|
entity |
| Predicate | appealableTo |
P17875
|
FINISHED |
| Object | Corte de Apelaciones |
—
|
NE NERFINISHED |
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: Corte de Apelaciones | Statement: [Tribunales de Juicio Oral en lo Penal, appealableTo, Corte de Apelaciones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealableTo Context triple: [Tribunales de Juicio Oral en lo Penal, appealableTo, Corte de Apelaciones]
-
A.
canBeAppealedTo
chosen
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
B.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
C.
appealBasis
Indicates the grounds, reasons, or legal basis on which an appeal is made.
-
D.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
E.
appeal
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 1, 2026, 12:58 a.m.