Triple
T4182280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Petersburg Oblast |
E88221
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Priozersk |
E247277
|
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: Priozersk | Statement: [Saint Petersburg Oblast, contains, Priozersk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Priozersk Context triple: [Saint Petersburg Oblast, contains, Priozersk]
-
A.
Priozersk
chosen
Priozersk is a small town in northwestern Russia known for its historic fortress Korela and its location on the shores of Lake Ladoga.
-
B.
Votkinsk
Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
-
C.
Podolsk
Podolsk is a major industrial city and former center of machine-building located just south of Moscow in western Russia.
-
D.
Pirogovo
Pirogovo is a settlement located near the Pirogovskoye Reservoir, known as a local residential and recreational area.
-
E.
Astapovo
Astapovo is a small Russian railway station village historically known as the place where the writer Leo Tolstoy died in 1910.
- 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_69bd7f60b49481908b2199544868769c |
completed | March 20, 2026, 5:09 p.m. |
Created at: March 9, 2026, 3:45 p.m.