Triple
T27764979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German theatre of the Thirty Years' War |
E701575
|
entity |
| Predicate | includedSiege |
P101059
|
FINISHED |
| Object | Siege of Magdeburg (1631) |
—
|
NE NERFINISHED |
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: Siege of Magdeburg (1631) | Statement: [German theatre of the Thirty Years' War, includedSiege, Siege of Magdeburg (1631)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedSiege Context triple: [German theatre of the Thirty Years' War, includedSiege, Siege of Magdeburg (1631)]
-
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.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
-
D.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
-
E.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 27, 2026, 4:30 p.m.