Triple

T16496630
Position Surface form Disambiguated ID Type / Status
Subject Mirny, Arkhangelsk Oblast E400698 entity
Predicate linkedTransport P113695 FINISHED
Object rail connections via Plesetskaya railway station 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: rail connections via Plesetskaya railway station | Statement: [Mirny, Arkhangelsk Oblast, linkedTransport, rail connections via Plesetskaya railway station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linkedTransport
Context triple: [Mirny, Arkhangelsk Oblast, linkedTransport, rail connections via Plesetskaya railway station]
  • A. linkedSupport
    Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
  • B. transportLinkType chosen
    Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
  • C. linkedNetwork
    Indicates that two entities are connected through a shared or associated network relationship.
  • D. linkedLocation
    Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
  • E. linkType
    Indicates the specific kind or category of relationship that connects two linked entities.
  • 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_69d88381f6148190819958a038be990e completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32e343a7c81909e04cbaaa40e2531 completed April 18, 2026, 7:09 a.m.
PD Predicate disambiguation batch_69e296902d6c8190884ddb612b8c5b36 completed April 17, 2026, 8:22 p.m.
Created at: April 10, 2026, 5:14 a.m.