Triple
T33813845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowogeorgiewsk Fortress |
E866612
|
entity |
| Predicate | siegeEvent |
P11070
|
FINISHED |
| Object | Siege of Nowogeorgiewsk (World War I) |
—
|
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 Nowogeorgiewsk (World War I) | Statement: [Nowogeorgiewsk Fortress, siegeEvent, Siege of Nowogeorgiewsk (World War I)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siegeEvent Context triple: [Nowogeorgiewsk Fortress, siegeEvent, Siege of Nowogeorgiewsk (World War I)]
-
A.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
B.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
C.
isSiegeOf
chosen
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
D.
typeOfSiege
Indicates the specific kind or category of siege involved in a conflict or military operation.
-
E.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fff18c648190bc0ea104b96b628d |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.