Triple
T33155603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Modder River |
E848564
|
entity |
| Predicate | relatedSiege |
—
|
GENERATED |
| Object | Siege of Kimberley |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSiege Context triple: [Battle of the Modder River, relatedSiege, Siege of Kimberley]
-
A.
siegeRelated
chosen
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
B.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
C.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
D.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
-
E.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
- F. None of above.
Provenance (1 batch)
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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.