Triple
T11195604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smolensk War |
E264912
|
entity |
| Predicate | usedFortificationType |
P66714
|
FINISHED |
| Object | bastion fortress |
—
|
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: bastion fortress | Statement: [Smolensk War, usedFortificationType, bastion fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFortificationType Context triple: [Smolensk War, usedFortificationType, bastion fortress]
-
A.
usedFortificationsAt
chosen
Indicates that an entity employed or deployed specific fortifications in a particular context, such as a battle, campaign, or defensive situation.
-
B.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
C.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
D.
eraOfFortification
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
E.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8bf14e481908563b15790af4d20 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.