Triple
T11734207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kokenhausen |
E278983
|
entity |
| Predicate | siegeRelated |
P101059
|
FINISHED |
| Object | relief of the Swedish siege of Kokenhausen |
—
|
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: relief of the Swedish siege of Kokenhausen | Statement: [Battle of Kokenhausen, siegeRelated, relief of the Swedish siege of Kokenhausen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siegeRelated Context triple: [Battle of Kokenhausen, siegeRelated, relief of the Swedish siege of Kokenhausen]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
-
C.
typeOfSiege
Indicates the specific kind or category of siege involved in a conflict or military operation.
-
D.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
E.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
- F. None of above. chosen
Provenance (4 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.