Triple
T31447176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Peralejo |
E802221
|
entity |
| Predicate | CubanObjective |
P172242
|
FINISHED |
| Object | weaken Spanish command and disrupt troop movements |
—
|
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: weaken Spanish command and disrupt troop movements | Statement: [Battle of Peralejo, CubanObjective, weaken Spanish command and disrupt troop movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CubanObjective Context triple: [Battle of Peralejo, CubanObjective, weaken Spanish command and disrupt troop movements]
-
A.
CubanCommander
Indicates that an individual holds a commanding or leadership military role associated with Cuba.
-
B.
MexicanObjective
Indicates that an entity has an objective, goal, or target specifically related to Mexico or Mexican affairs.
-
C.
stanceOnUSPolicyTowardCuba
Indicates a subject’s expressed position or viewpoint regarding the United States’ policies toward Cuba.
-
D.
politicalPositionOnCuba
Indicates a stance, view, or policy position that an entity holds regarding Cuba or Cuba-related issues.
-
E.
SovietObjective
Indicates that the entity represents a goal, target, or strategic aim pursued by the Soviet Union.
- F. None of above. chosen
Provenance (4 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:10 p.m.