Triple
T5660960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Participation in the Battle of San Domingo |
E124737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military engagement participation |
C8259
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: military engagement participation Context triple: [Participation in the Battle of San Domingo, instanceOf, military engagement participation]
-
A.
military confrontation
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
B.
participants in military alliance
Participants in a military alliance are sovereign states or entities that formally agree to cooperate in defense and security matters, sharing obligations, resources, and strategic commitments against common threats.
-
C.
military intervention
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
-
D.
military event
chosen
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
E.
engagement of the Falklands War
The engagement of the Falklands War is a military operation or battle between British and Argentine forces during the 1982 conflict over the Falkland Islands, characterized by specific objectives, participating units, tactics, and outcomes within the broader campaign.
- F. None of above.
Provenance (1 batch)
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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
Created at: March 22, 2026, 3:42 p.m.