Triple

T16308371
Position Surface form Disambiguated ID Type / Status
Subject Володарский мост E395979 entity
Predicate instanceOf P0 FINISHED
Object мост C22181 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: мост
Context triple: [Володарский мост, instanceOf, мост]
  • A. bridge operator
    A bridge operator is an entity responsible for managing and controlling the operation, safety, and coordination of a bridge’s movable or functional components to ensure efficient and secure passage for users.
  • B. river bridge chosen
    A river bridge is a structure built to span a river, providing a stable pathway for vehicles, pedestrians, or rail traffic to cross from one bank to the other.
  • C. multipurpose bridge
    A multipurpose bridge is a structural crossing designed to support multiple concurrent uses—such as vehicular traffic, pedestrians, cyclists, utilities, and sometimes public spaces or transit systems—within a single integrated infrastructure.
  • D. dam bridge
    A dam bridge is a structure that combines the functions of a dam for water retention and control with a bridge that provides a transportation route across the impounded water or river.
  • E. bridge in Moscow
    A bridge in Moscow is a structural crossing over the Moskva River or other waterways in the city, serving both transportation needs and often acting as an architectural landmark within the urban landscape.
  • F. None of above.

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_69d87f23bb088190a16fbb91a1957ea5 completed April 10, 2026, 4:40 a.m.
Created at: April 10, 2026, 5:06 a.m.