Triple
T37303165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central El Salvador |
E926007
|
entity |
| Predicate | conflictAffectedRegionIn |
P34508
|
FINISHED |
| Object | Salvadoran Civil War |
—
|
NE NERFINISHED |
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: Salvadoran Civil War | Statement: [Central El Salvador, conflictAffectedRegionIn, Salvadoran Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictAffectedRegionIn Context triple: [Central El Salvador, conflictAffectedRegionIn, Salvadoran Civil War]
-
A.
conflictRegion
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
B.
regionOfConflict
chosen
Indicates that a specified region is the location where a particular conflict or dispute takes place.
-
C.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
D.
affectedSyrianRegion
Indicates that a specified Syrian region is impacted or influenced by a particular event, condition, or action.
-
E.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.