Triple

T31675148
Position Surface form Disambiguated ID Type / Status
Subject Хорошёвская E808379 entity
Predicate линия P172405 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. divisionLine
    Indicates a boundary or separating line that divides one area, group, or portion from another.
  • B. lineType
    Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
  • C. yardLine
    Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
  • D. lineStandard
    Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
  • E. connectedLine
    Indicates that two entities are joined by a continuous line or linear connection.
  • F. None of above. chosen

Provenance (4 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_69f6abe15d5c81909ccf4ce37f78bc43 completed May 3, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69f6aa20a1588190a53533fc9764efb2 completed May 3, 2026, 1:51 a.m.
PDg Predicate description generation batch_69f6aaf31a548190b2f792ff4b8c002a completed May 3, 2026, 1:54 a.m.
Created at: April 30, 2026, 11:02 p.m.