Triple
T16289726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khimki lock system |
E395486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | navigation lock system |
C37223
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: navigation lock system Context triple: [Khimki lock system, instanceOf, navigation lock system]
-
A.
navigation system
A navigation system is a coordinated set of hardware and software components that determines a user's position and provides optimal routes and guidance to reach desired destinations.
-
B.
navigator
A navigator is an entity responsible for determining and directing the optimal path or course from a starting point to a desired destination using available information and tools.
-
C.
navigational passage
A navigational passage is a corridor, channel, or route—often within a building, vessel, or geographic area—designed to guide movement safely and efficiently from one location to another.
-
D.
park system
A park system is an organized network of public parks and green spaces managed collectively to provide recreation, conservation, and aesthetic benefits to a community or region.
-
E.
lock flight
A lock flight is a series of canal locks arranged consecutively to raise or lower boats over a significant change in water level within a short distance.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: April 10, 2026, 5:05 a.m.