Triple
T6445362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boer–Zulu conflicts |
E138327
|
entity |
| Predicate | involvesTypeOfWarfare |
P1403
|
FINISHED |
| Object | frontier 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: frontier warfare | Statement: [Boer–Zulu conflicts, involvesTypeOfWarfare, frontier warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTypeOfWarfare Context triple: [Boer–Zulu conflicts, involvesTypeOfWarfare, frontier warfare]
-
A.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
C.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
D.
involvesWeaponType
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698d866c81909ef3e0a53833ff7d |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.