Triple
T7806655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cúcuta |
E180571
|
entity |
| Predicate | combatantStrengthPatriots |
P69561
|
FINISHED |
| Object | approximately 400–500 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 400–500 men | Statement: [Battle of Cúcuta, combatantStrengthPatriots, approximately 400–500 men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantStrengthPatriots Context triple: [Battle of Cúcuta, combatantStrengthPatriots, approximately 400–500 men]
-
A.
primaryPatriotForce
Indicates that an entity serves as the main or leading patriotic force in a given context or struggle.
-
B.
patriotForceType
Indicates the type or category of force associated with a patriot or patriotic group (e.g., military, paramilitary, civilian).
-
C.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
-
D.
strengthPatriots
chosen
Indicates a relationship where the strength, power, or capability associated with a group referred to as "Patriots" is being expressed or evaluated.
-
E.
PatriotCasualties
Indicates that the event involves casualties suffered by patriot forces or supporters.
- 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.