Triple
T3873438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Canal |
E92439
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | 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: Khimki | Statement: [Moscow Canal, passesNear, Khimki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khimki Context triple: [Moscow Canal, passesNear, 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.
Astapovo
Astapovo is a small Russian railway station village historically known as the place where the writer Leo Tolstoy died in 1910.
-
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.
Odintsovo
Odintsovo is a town in western Russia that serves as an important suburban center just outside Moscow.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec581adc81909219e6f025fc97c2 |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b52840f9b4819098fa220189222210 |
completed | March 14, 2026, 9:20 a.m. |
Created at: March 9, 2026, 3:20 p.m.