Triple
T7806656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cúcuta |
E180571
|
entity |
| Predicate | combatantStrengthRoyalists |
P20427
|
FINISHED |
| Object | approximately 800–900 men |
—
|
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: approximately 800–900 men | Statement: [Battle of Cúcuta, combatantStrengthRoyalists, approximately 800–900 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantStrengthRoyalists Context triple: [Battle of Cúcuta, combatantStrengthRoyalists, approximately 800–900 men]
-
A.
RoyalistForceStrength
chosen
Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
-
B.
royalistForcesIncluded
Indicates that the composition of the royalist forces included the specified entity or group.
-
C.
RoyalistCasualties
Indicates the number or occurrence of casualties suffered by Royalist forces in a given conflict or event.
-
D.
RoyalistSide
Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict or context.
-
E.
primaryRoyalistCavalryLeader
Indicates that someone serves as the main commanding leader of cavalry forces aligned with the Royalist side.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:35 p.m.