Triple
T22255152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comadres (Committee of Mothers) in El Salvador |
E550077
|
entity |
| Predicate | victimFocus |
P699
|
FINISHED |
| Object | disappeared persons |
—
|
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: disappeared persons | Statement: [Comadres (Committee of Mothers) in El Salvador, victimFocus, disappeared persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimFocus Context triple: [Comadres (Committee of Mothers) in El Salvador, victimFocus, disappeared persons]
-
A.
victimCategory
Indicates the classification or type of victim associated with an event, action, or harmful outcome.
-
B.
victimGroup
chosen
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
C.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
D.
victimGroupContext
Indicates the contextual circumstances or setting in which a victim group is targeted, affected, or involved in an event or action.
-
E.
victimParty
Indicates that one party is the victim or harmed side in an event, action, or situation involving another party.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c1d70881908df47b0f818c0022 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.