Triple
T28437899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Pskov (1581–1582) |
E715620
|
entity |
| Predicate | attackedFortification |
P102873
|
FINISHED |
| Object | Pskov fortress |
—
|
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: Pskov fortress | Statement: [Siege of Pskov (1581–1582), attackedFortification, Pskov fortress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackedFortification Context triple: [Siege of Pskov (1581–1582), attackedFortification, Pskov fortress]
-
A.
fortificationTypeAssaulted
chosen
Indicates that an assault or attack was carried out against a specific type of fortification.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
opposedFortification
Indicates that one entity actively resisted, challenged, or worked against the strengthening or fortifying of another entity or location.
-
D.
garrisonAttacked
Indicates that a military garrison was subjected to an attack by another force or entity.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e3b35fc819096c20346642c2a38 |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:44 a.m.