Triple

T37901675
Position Surface form Disambiguated ID Type / Status
Subject Финляндский вокзал E945429 entity
Predicate имеетСообщениеС P191417 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. isCommunicatedDuring
    Indicates that one entity (such as information, a message, or content) is conveyed or transmitted in the course of a specified event, process, or time period.
  • B. hasSocialMessage
    Indicates that something conveys, promotes, or is associated with a broader social, ethical, or political message.
  • C. hasMessenger
    Indicates that one entity uses or is associated with another entity as a messenger or intermediary for communication.
  • D. correspondedWith
    Indicates that two entities engaged in mutual communication, typically by exchanging messages or letters over a period of time.
  • E. hasCommunicationType
    Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
  • 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_69f76ef20bb0819088b5b6ceecb0b8fc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fcdf2394748190b35cead3e208447d completed May 7, 2026, 6:51 p.m.
PD Predicate disambiguation batch_69fcdbe344ec8190a0471911952f4b82 completed May 7, 2026, 6:37 p.m.
PDg Predicate description generation batch_69fcdf22ab8881908b257f16522920c5 completed May 7, 2026, 6:51 p.m.
Created at: May 3, 2026, 4:20 p.m.