Triple

T19419120
Position Surface form Disambiguated ID Type / Status
Subject Bolshoy Moskvoretsky Bridge E485798 entity
Predicate isLocatedOnRiverSection P58979 FINISHED
Object central Moscow reach of Moskva River LITERAL 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: central Moscow reach of Moskva River | Statement: [Bolshoy Moskvoretsky Bridge, isLocatedOnRiverSection, central Moscow reach of Moskva River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLocatedOnRiverSection
Context triple: [Bolshoy Moskvoretsky Bridge, isLocatedOnRiverSection, central Moscow reach of Moskva River]
  • A. locatedInRiverArea
    Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
  • B. watercourseSectionOf
    Indicates that a watercourse segment forms a constituent part of a larger watercourse.
  • C. isOnWatercourse chosen
    Indicates that one entity is situated directly on, above, or along the path of a watercourse such as a river, stream, or canal.
  • D. downstreamRiverSection
    Indicates that one river section is located downstream from, and receives flow from, another river section.
  • E. positionInRiverSystem
    Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
  • F. None of above.

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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62afbaf0c8190913eda4b04efbe67 completed April 20, 2026, 1:32 p.m.
PD Predicate disambiguation batch_69e4fd68b1f881908d273de1fee81a75 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:37 p.m.