Triple
T31705202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESMA detention center |
E809158
|
entity |
| Predicate | methodOfRepression |
P79501
|
FINISHED |
| Object | sexual violence |
—
|
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: sexual violence | Statement: [ESMA detention center, methodOfRepression, sexual violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfRepression Context triple: [ESMA detention center, methodOfRepression, sexual violence]
-
A.
methodOfPersecution
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
B.
associatedWithRepressionSystem
Indicates that an entity is connected to, involved in, or part of a system or mechanism used for repression or suppressive control.
-
C.
useOfTorture
chosen
Indicates the intentional infliction or use of torture by one entity upon another, typically to punish, coerce, intimidate, or extract information.
-
D.
punishmentMethod
Indicates the method or means by which a punishment is carried out on an entity.
-
E.
notableRepressionEvent
Indicates a significant instance in which an entity engaged in or experienced systematic repression, such as suppression of rights, freedoms, or dissent.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:13 p.m.