Triple
T25779704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosnian Croat leadership |
E649252
|
entity |
| Predicate | foundResponsibleFor |
P636
|
FINISHED |
| Object | joint criminal enterprise |
—
|
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: joint criminal enterprise | Statement: [Bosnian Croat leadership, foundResponsibleFor, joint criminal enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundResponsibleFor Context triple: [Bosnian Croat leadership, foundResponsibleFor, joint criminal enterprise]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
foundResponsibleParty
Indicates that an entity has identified or determined which party is responsible for a particular action, event, or obligation.
-
C.
blamedOn
Indicates that responsibility or fault for something is assigned to a particular entity.
-
D.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
E.
foundCrownLiable
Indicates that a legal decision has determined the Crown (the state) to be responsible or at fault in a particular case.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 5:37 a.m.