Triple
T16289741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khimki lock system |
E395486
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | city of Khimki |
E52717
|
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: city of Khimki | Statement: [Khimki lock system, near, city of Khimki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Khimki Context triple: [Khimki lock system, near, city of Khimki]
-
A.
Khimki
chosen
Khimki is a city in Moscow Oblast, Russia, forming part of the Moscow metropolitan area and known for its proximity to major transport hubs and industrial facilities.
-
B.
Krylatskoye
Krylatskoye is a Moscow Metro station serving the Krylatskoye District in western Moscow, Russia.
-
C.
Aeroport District, Moscow
Aeroport District is a residential and commercial neighborhood in Moscow’s Northern Administrative Okrug, known for its Soviet-era architecture, transport links, and proximity to former aviation and industrial sites.
-
D.
Khimki Urban Okrug
Khimki Urban Okrug is a municipal formation in Moscow Oblast, Russia, encompassing the city of Khimki and its surrounding territories as a single urban administrative unit.
-
E.
Medvedkovo
Medvedkovo is a Moscow Metro station serving as the northeastern terminus of the Kaluzhsko–Rizhskaya Line.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e249175e24819082e571039e278056 |
completed | April 17, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f94ede48190835e8a0c6f5d0f19 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:05 a.m.