Triple

T35429993
Position Surface form Disambiguated ID Type / Status
Subject Sviblovo E1024028 entity
Predicate adjacentStationOnKaluzhsko–RizhskayaLine P191724 FINISHED
Object Botanichesky Sad 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: Botanichesky Sad | Statement: [Sviblovo, adjacentStationOnKaluzhsko–RizhskayaLine, Botanichesky Sad]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentStationOnKaluzhsko–RizhskayaLine
Context triple: [Sviblovo, adjacentStationOnKaluzhsko–RizhskayaLine, Botanichesky Sad]
  • A. hasAdjacentStationOnKoltsevayaLine
    Indicates that one station is directly next to another station on the Koltsevaya (circle) metro line.
  • B. adjacentStationOnCapitalLine
    Indicates that one station is directly next to another station along the Capital Line, with no other stations in between.
  • C. adjacentStationOnSilverLine
    Indicates that one station is directly next to another station along the Silver Line, with no other stations in between.
  • D. adjacentStationOnRedLine
    Indicates that one station is directly next to another station along the Red Line, with no other stations in between.
  • E. adjacentStationOnPinkLine
    Indicates that one station is directly next to another station along the Pink Line route.
  • 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_69f76df743c48190aecb6dd79efb0d95 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fce7671f108190bf3ebf54339068b5 completed May 7, 2026, 7:26 p.m.
PD Predicate disambiguation batch_69fce5b5a84c81908ac1b5b9f08d48d0 completed May 7, 2026, 7:19 p.m.
PDg Predicate description generation batch_69fce76669408190b1beef8899a8a5e2 completed May 7, 2026, 7:26 p.m.
Created at: May 3, 2026, 4:03 p.m.