Triple

T34553754
Position Surface form Disambiguated ID Type / Status
Subject Paveletskaya (Koltsevaya line) E887144 entity
Predicate servesRailwayTerminal P103596 FINISHED
Object Paveletsky railway terminal 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: Paveletsky railway terminal | Statement: [Paveletskaya (Koltsevaya line), servesRailwayTerminal, Paveletsky railway terminal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesRailwayTerminal
Context triple: [Paveletskaya (Koltsevaya line), servesRailwayTerminal, Paveletsky railway terminal]
  • A. servedByRailwayTerminus
    Indicates that a place or location is provided rail transport services by a specific railway terminus.
  • B. railwayTerminalServed
    Indicates that a railway terminal is served by, or has service connections with, a particular railway line, route, or operator.
  • C. servesLocalTrains
    Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
  • D. connectsToRailStation
    Indicates that one entity has a direct link, route, or access connection to a rail station.
  • E. servesTransitFacility chosen
    Indicates that one entity provides service or operational support to a transit facility, such as a station, stop, or terminal.
  • 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_69f349cff89081908f91e0b064f4833e completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ffc1550cb481908628e446d9b67f7b completed May 9, 2026, 11:20 p.m.
PD Predicate disambiguation batch_69ffc10a74708190ae90e2c378791f70 completed May 9, 2026, 11:19 p.m.
Created at: May 1, 2026, 2:02 a.m.