Triple

T38377867
Position Surface form Disambiguated ID Type / Status
Subject Дворцовый мост E893673 entity
Predicate расположенВышеПоТечениюОт P63897 FINISHED
Object Троицкий мост 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: Троицкий мост | Statement: [Дворцовый мост, расположенВышеПоТечениюОт, Троицкий мост]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: расположенВышеПоТечениюОт
Context triple: [Дворцовый мост, расположенВышеПоТечениюОт, Троицкий мост]
  • A. situatedUpstreamOf chosen
    Indicates that one entity is located in the direction from which a flow (such as water, traffic, or a process stream) originates relative to another entity along the same path or system.
  • B. 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).
  • C. upstreamRiver
    Indicates that one river is located or flows in an upstream direction relative to another river within the same watercourse system.
  • D. waterwayDirection
    Indicates the directional flow or orientation of a waterway relative to a reference point or path.
  • E. расположенаНа
    Indicates that one entity is located on the surface or area of another entity.
  • 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_69f76e4b1f748190a380696a16eae4a2 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcd1499e2c81909bafd84dc4810f45 completed May 7, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69fcccf024ec819086383ffbb6cfc036 completed May 7, 2026, 5:33 p.m.
Created at: May 3, 2026, 4:31 p.m.