Triple
T16141722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plains (later period) |
E391672
|
entity |
| Predicate | warfarePattern |
P1403
|
FINISHED |
| Object | mounted raiding |
—
|
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: mounted raiding | Statement: [Plains (later period), warfarePattern, mounted raiding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warfarePattern Context triple: [Plains (later period), warfarePattern, mounted raiding]
-
A.
warfareType
chosen
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
B.
functionInWarfare
Indicates the role, purpose, or operational function that something serves within a military or warfare context.
-
C.
opposedWarfareType
Indicates that one entity is in opposition to, or acts against, the type or form of warfare represented by the other entity.
-
D.
usedWarfareType
Indicates the specific type or method of warfare that an entity employed in a conflict or military context.
-
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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a087c848190aba9ed2ccb422427 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.