Triple

T31675157
Position Surface form Disambiguated ID Type / Status
Subject Хорошёвская E808379 entity
Predicate транспортнаяСистема P941 FINISHED
Object Московский метрополитен NE NERFINISHED

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. complementsTransportSystem
    Indicates that one transport-related entity enhances, supports, or improves the effectiveness of another transport system without replacing it.
  • B. typeOfTransportInfrastructure
    Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
  • C. hasTransportationSystem chosen
    Indicates that an entity possesses, operates, or is served by an organized system for transporting people or goods.
  • D. rapidTransitSystem
    Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
  • E. transportation
    Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
  • 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_69f348dcf5d48190ac25b1365ae717a8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6aaf50be08190a2b62a6d881f8aee completed May 3, 2026, 1:55 a.m.
PD Predicate disambiguation batch_69f6aa20a1588190a53533fc9764efb2 completed May 3, 2026, 1:51 a.m.
Created at: April 30, 2026, 11:02 p.m.