Triple
T38156990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guazapa |
E952911
|
entity |
| Predicate | hasConflictPeriod |
P28865
|
FINISHED |
| Object | 1980–1992 Salvadoran Civil War |
—
|
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: 1980–1992 Salvadoran Civil War | Statement: [Guazapa, hasConflictPeriod, 1980–1992 Salvadoran Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConflictPeriod Context triple: [Guazapa, hasConflictPeriod, 1980–1992 Salvadoran Civil War]
-
A.
hasOngoingConflict
Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
-
B.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
C.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
hasConflictSide
Indicates that an entity participates as a specific side or party in a conflict or dispute.
-
E.
hasRoleInConflict
Indicates that an entity holds or held a specific role, position, or function within a particular conflict or dispute.
- 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.