Triple
T9186470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Abu Klea |
E220471
|
entity |
| Predicate | MahdistStrength |
P36039
|
FINISHED |
| Object | several thousand warriors |
—
|
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: several thousand warriors | Statement: [Battle of Abu Klea, MahdistStrength, several thousand warriors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MahdistStrength Context triple: [Battle of Abu Klea, MahdistStrength, several thousand warriors]
-
A.
MoroccanStrengthApprox
Indicates an approximate assessment or estimation of the strength associated with Morocco or Moroccan-related entities.
-
B.
MamlukCommander
Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
-
C.
hizb
Indicates a relationship in which an entity is affiliated with, belongs to, or is associated with a political party or organized group.
-
D.
Dhul-HulayfahFor
Indicates that something is designated for, associated with, or intended to be used in relation to Dhul-Hulayfah.
-
E.
commandingForce2Strength
chosen
Indicates that a commanding force possesses or exerts a particular level or measure of strength.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31a52508190a83ccd76f3aa039b |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.