Triple
T1918436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Khartoum |
E40070
|
entity |
| Predicate | defenderForce |
P15009
|
FINISHED |
| Object | Egyptian garrison |
—
|
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: Egyptian garrison | Statement: [Siege of Khartoum, defenderForce, Egyptian garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenderForce Context triple: [Siege of Khartoum, defenderForce, Egyptian garrison]
-
A.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
B.
defenceHandledBy
chosen
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
C.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
commanderForDefender
Indicates that an entity serves as the commanding officer or leader responsible for directing and overseeing a defending force or defender.
-
E.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb211eda88190865de7a0522a453d |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.