Triple
T15533354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Stolbovo |
E370278
|
entity |
| Predicate | concludedIn |
P2818
|
FINISHED |
| Object | Stolbovo |
E800801
|
NE 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: Stolbovo | Statement: [Treaty of Stolbovo, concludedIn, Stolbovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stolbovo Context triple: [Treaty of Stolbovo, concludedIn, Stolbovo]
-
A.
Stolbovo
chosen
Stolbovo is a village in northwestern Russia historically notable as the site where the 1617 Treaty of Stolbovo ended the Ingrian War between Sweden and Russia.
-
B.
Pestovo
Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
-
C.
Kozelsk
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
-
D.
Lyudinovo
Lyudinovo is an industrial town in western Russia known for its engineering and manufacturing sectors.
-
E.
Pleskov
Pleskov is an alternative historical or variant name for the Russian city of Pskov, a historic regional center in northwestern Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414877d88190804ee76566004e13 |
completed | April 16, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d5e82a48190bb0a10ebc2412129 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 4:06 a.m.