Triple
T30578526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azimjan Askarov |
E778316
|
entity |
| Predicate | detentionAllegations |
P83746
|
FINISHED |
| Object | torture in custody |
—
|
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: torture in custody | Statement: [Azimjan Askarov, detentionAllegations, torture in custody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detentionAllegations Context triple: [Azimjan Askarov, detentionAllegations, torture in custody]
-
A.
detainsUnder
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
B.
hasAllegationsOf
chosen
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
-
C.
deniedAllegations
Indicates that one party has rejected or refuted specific accusations made against them.
-
D.
detentionWithoutCharge
Indicates that an entity is being held in custody by authorities without having formal charges filed against them.
-
E.
detentionEvent
Indicates an event in which an entity is formally held, confined, or kept in custody, typically by an authority, for a period of time.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689406a2c8190bd9b1fe2813478a5 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.