Triple
T18172142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusto César Sandino |
E435057
|
entity |
| Predicate | startOfGuerrillaCampaign |
P40176
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [Augusto César Sandino, startOfGuerrillaCampaign, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfGuerrillaCampaign Context triple: [Augusto César Sandino, startOfGuerrillaCampaign, 1927]
-
A.
armedStruggleStart
Indicates the point in time when an organized group initiates the use of armed force or violence as a method of struggle or conflict.
-
B.
startOfMajorCampaign
Indicates that the referenced event marks the beginning of a significant, large-scale campaign or operation.
-
C.
startDateAsGuerrilla
chosen
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
D.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
E.
armedStruggleAgainst
Indicates an organized, often violent resistance or conflict carried out by one party using weapons against another party, typically to oppose or overthrow its control or policies.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df56d0a88190af3f407d2a3bb74f |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.