Triple
T16868748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Boruszkowce |
E410111
|
entity |
| Predicate | useOfForce |
P44969
|
FINISHED |
| Object | conventional warfare |
—
|
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: conventional warfare | Statement: [Battle of Boruszkowce, useOfForce, conventional warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfForce Context triple: [Battle of Boruszkowce, useOfForce, conventional warfare]
-
A.
typeOfUseOfForce
chosen
Indicates the specific manner or category of force applied in an interaction or incident.
-
B.
militaryForceUsed
Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
-
C.
authorizedUseOfForce
Indicates that an entity has been granted legitimate permission to apply physical force under specified conditions or authority.
-
D.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
-
E.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50a82348190b3e33fd558aa3c7f |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.