Triple
T4182283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Petersburg Oblast |
E88221
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sosnovy Bor |
E219962
|
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: Sosnovy Bor | Statement: [Saint Petersburg Oblast, contains, Sosnovy Bor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sosnovy Bor Context triple: [Saint Petersburg Oblast, contains, Sosnovy Bor]
-
A.
Sosnovy Bor
chosen
Sosnovy Bor is a Russian coastal town on the Gulf of Finland known for its large nuclear power plant and role as an energy and industrial center.
-
B.
Skovorodino
Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
-
C.
Borovichi
Borovichi is a town in western Russia known as an industrial and transport center situated on the Msta River.
-
D.
Kastornoye
Kastornoye is a locality in Russia historically notable as the namesake and focal area of the Voronezh–Kastornoye military offensive during World War II.
-
E.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0305e2e88190a51f176f8534f1f9 |
completed | March 9, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b65f1b86908190965342d8da0ff545 |
completed | March 15, 2026, 7:26 a.m. |
Created at: March 9, 2026, 3:45 p.m.