Triple
T31639033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICTR Trial Chamber I |
E807392
|
entity |
| Predicate | subjectToAppealBody |
P17875
|
FINISHED |
| Object | ICTR Appeals Chamber |
—
|
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: ICTR Appeals Chamber | Statement: [ICTR Trial Chamber I, subjectToAppealBody, ICTR Appeals Chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToAppealBody Context triple: [ICTR Trial Chamber I, subjectToAppealBody, ICTR Appeals Chamber]
-
A.
decisionSubjectToAppealOn
Indicates that a particular decision is open to being challenged or reviewed through an appeal process.
-
B.
contestedBody
Indicates that an entity is the subject of a dispute, challenge, or disagreement between parties over its control, status, or validity.
-
C.
reasonForAppealDecision
Indicates the justification or grounds cited for making a particular appeal decision.
-
D.
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.
-
E.
cannotBeAppealed
Indicates that a decision, ruling, or outcome is final and cannot be challenged or reviewed through an appeal process.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 30, 2026, 10:48 p.m.