Triple
T33368464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prosecutor v. Duško Tadić |
E854419
|
entity |
| Predicate | trialChamber |
P9881
|
FINISHED |
| Object | Trial Chamber II of the ICTY |
—
|
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: Trial Chamber II of the ICTY | Statement: [Prosecutor v. Duško Tadić, trialChamber, Trial Chamber II of the ICTY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialChamber Context triple: [Prosecutor v. Duško Tadić, trialChamber, Trial Chamber II of the ICTY]
-
A.
courtroom
Indicates a relationship where a legal proceeding or judicial action takes place within or is associated with a specific courtroom.
-
B.
trialHeld
Indicates that a formal legal proceeding or court trial has taken place regarding a particular case or dispute.
-
C.
trialInstance
Indicates that one entity is a specific occurrence or execution of a broader trial, experiment, or test.
-
D.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
-
E.
trialCourt
chosen
Indicates that a legal matter, decision, or proceeding is associated with, handled by, or occurring in a court of first instance (the trial-level court).
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:35 a.m.