Triple
T9461811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kafirs of Kafiristan |
E228162
|
entity |
| Predicate | warfare |
P12
|
FINISHED |
| Object | raiding of neighboring areas |
—
|
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: raiding of neighboring areas | Statement: [Kafirs of Kafiristan, warfare, raiding of neighboring areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfare Context triple: [Kafirs of Kafiristan, warfare, raiding of neighboring areas]
-
A.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
militaryConflict
chosen
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
warName
Indicates the specific name or title assigned to a particular war or armed conflict.
-
D.
majorWar
Indicates a large-scale, intense armed conflict between major powers or involving substantial military forces and widespread impact.
-
E.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcc8b1881908aa6ee13ab195330 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.