Triple

T38377866
Position Surface form Disambiguated ID Type / Status
Subject Дворцовый мост E893673 entity
Predicate имеетРазводнойМеханизм P134343 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. hasSlidingMechanism
    Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
  • B. hasMechanicalFeature chosen
    Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
  • C. hasCurtainMechanism
    Indicates that one entity is equipped with or includes a mechanism for operating a curtain.
  • D. tiltingMechanism
    Indicates a relationship where one entity serves as a mechanism that enables another entity to tilt or be tilted.
  • E. hasRotationMechanic
    Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
  • 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_69fcf825ca7081909d06b0df33eb33f9 completed May 7, 2026, 8:37 p.m.
PD Predicate disambiguation batch_69fcf42160f0819096812a8bf590875e completed May 7, 2026, 8:20 p.m.
Created at: May 3, 2026, 4:31 p.m.