Triple
T13775698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khanty-Mansiysk |
E330998
|
entity |
| Predicate | foundedAs |
P364
|
FINISHED |
| Object | Samarovo |
E1074941
|
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: Samarovo | Statement: [Khanty-Mansiysk, foundedAs, Samarovo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samarovo Context triple: [Khanty-Mansiysk, foundedAs, Samarovo]
-
A.
Samarovo
chosen
Samarovo is the historical settlement that later became part of the modern Russian city of Khanty-Mansiysk in Western Siberia.
-
B.
Makeyevka
Makeyevka is an industrial city in eastern Ukraine’s Donetsk Oblast, historically known for its coal mining and metallurgical industries.
-
C.
Podporozhye
Podporozhye is a town in northwestern Russia situated within Leningrad (Saint Petersburg) Oblast, known for its location along the Svir River.
-
D.
Samokov
Samokov is a Bulgarian town in the Rila Mountains known historically for its ironworking and as a gateway to nearby ski and hiking areas.
-
E.
Konakovo
Konakovo is a town in Tver Oblast, Russia, situated on the Volga River and known for its power station and riverside recreation.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0238bdbc8190a946e6e5431632a5 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb64655b08190befaf404ef378a8c |
completed | May 7, 2026, 3:56 p.m. |
Created at: April 9, 2026, 10:10 p.m.