Triple
T38156967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guazapa |
E952911
|
entity |
| Predicate | wasGuerrillaStrongholdDuring |
P85412
|
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: [Guazapa, wasGuerrillaStrongholdDuring, Salvadoran Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasGuerrillaStrongholdDuring Context triple: [Guazapa, wasGuerrillaStrongholdDuring, Salvadoran Civil War]
-
A.
timeAsGuerrillaStronghold
chosen
Indicates the period during which a location functioned as a base or stronghold for guerrilla forces.
-
B.
garrisonedDuring
Indicates that a military force was stationed or quartered at a location for defense or control during a specified time period.
-
C.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
-
D.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
E.
wasKeyBattlegroundDuring
Indicates that a location served as an important site of conflict or struggle during a specified event or period.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.