Triple
T18517484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casanare campaign |
E452501
|
entity |
| Predicate | opposedControl |
P52508
|
FINISHED |
| Object | Spanish royalist control of Casanare region |
—
|
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: Spanish royalist control of Casanare region | Statement: [Casanare campaign, opposedControl, Spanish royalist control of Casanare region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedControl Context triple: [Casanare campaign, opposedControl, Spanish royalist control of Casanare region]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
oppositeControlledBy
Indicates that one entity is under the control or influence of another entity that is positioned or defined as its opposite or counterpart.
-
C.
opposedFocus
Indicates that one entity’s focus, attention, or emphasis is directed in opposition to, or in contrast with, the focus of another entity.
-
D.
opposedOperation
chosen
Indicates that one operation is in conflict with, counters, or works against another operation.
-
E.
opposedOutcome
Indicates that one entity’s outcome is in conflict with, counters, or works against the outcome associated with another entity.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338b2cd0819095db59f6bfc70814 |
completed | April 19, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.