Triple

T1339548
Position Surface form Disambiguated ID Type / Status
Subject Gostiny Dvor metro station E28432 entity
Predicate hasTransferCorridor P5520 FINISHED
Object pedestrian tunnel to Nevsky Prospekt metro 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: pedestrian tunnel to Nevsky Prospekt metro station | Statement: [Gostiny Dvor metro station, hasTransferCorridor, pedestrian tunnel to Nevsky Prospekt metro station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransferCorridor
Context triple: [Gostiny Dvor metro station, hasTransferCorridor, pedestrian tunnel to Nevsky Prospekt metro station]
  • A. hasCorridor chosen
    Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
  • B. hasTransfer
    Indicates a relationship where something is moved or conveyed from one entity or location to another.
  • C. hasServiceOnCorridor
    Indicates that a service operates along, or is provided on, a specific corridor or route.
  • D. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • E. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • 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_69a49854eb3481908c7d56b2e449a290 completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c21303c881908fef0b32831222fe completed March 1, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69a4bef3e8fc8190ac9a1ba9b5879483 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:56 p.m.