Triple
T21195011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior Court of Justice of Brazil |
E522303
|
entity |
| Predicate | typeOfAppealHandled |
P15240
|
FINISHED |
| Object | recurso especial |
—
|
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: recurso especial | Statement: [Superior Court of Justice of Brazil, typeOfAppealHandled, recurso especial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAppealHandled Context triple: [Superior Court of Justice of Brazil, typeOfAppealHandled, recurso especial]
-
A.
typeOfAppeals
chosen
Indicates the specific category or kind of appeals associated with or applied to a given case, decision, or legal action.
-
B.
handlesAppealsIn
Indicates that an entity is responsible for processing or adjudicating appeals within a specified jurisdiction, domain, or context.
-
C.
wasOverturnedByCourt
Indicates that a prior decision, ruling, or judgment was reversed or nullified by a court.
-
D.
hearsAppealsIn
Indicates that a judicial body has the authority to review and decide appeals within a specified jurisdiction or court.
-
E.
hearsAppealTo
Indicates that one entity formally reviews and considers an appeal submitted by another entity.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333aa0fc81909b17eb6a26f389ec |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.