Triple
T9602404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial Chambers (ICTY) |
E231879
|
entity |
| Predicate | hearsEvidenceFrom |
P27001
|
FINISHED |
| Object | prosecution |
—
|
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: prosecution | Statement: [Trial Chambers (ICTY), hearsEvidenceFrom, prosecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsEvidenceFrom Context triple: [Trial Chambers (ICTY), hearsEvidenceFrom, prosecution]
-
A.
hearsFrom
chosen
Indicates that one entity receives information, communication, or a message from another entity.
-
B.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
C.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
-
D.
hearsClaimsOn
Indicates that an entity formally receives and considers claims, complaints, or requests submitted by another entity.
-
E.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5af8f0819089408ed630afa812 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.