Triple
T11895570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kozelsk camp |
E283027
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kozelsk |
E498927
|
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: Kozelsk | Statement: [Kozelsk camp, locatedIn, Kozelsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kozelsk Context triple: [Kozelsk camp, locatedIn, Kozelsk]
-
A.
Kozelsk
chosen
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
-
B.
Borisoglebsk
Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
-
C.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
-
D.
Pleskov
Pleskov is an alternative historical or variant name for the Russian city of Pskov, a historic regional center in northwestern Russia.
-
E.
Zaraysk
Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1286808190949719f54ff49a01 |
completed | April 10, 2026, 11:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f43ff588f08190affc45b44b9e85e3 |
completed | May 1, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:44 p.m.