Triple

T37901665
Position Surface form Disambiguated ID Type / Status
Subject Финляндский вокзал E945429 entity
Predicate историческоеНазваниеЛинии P17520 FINISHED
Object Финляндская железная дорога 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: Финляндская железная дорога | Statement: [Финляндский вокзал, историческоеНазваниеЛинии, Финляндская железная дорога]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: историческоеНазваниеЛинии
Context triple: [Финляндский вокзал, историческоеНазваниеЛинии, Финляндская железная дорога]
  • A. lineName
    Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
  • B. isWesternTerminusOfHistoricLine
    Indicates that something serves as the western endpoint of a historically significant route, line, or transportation corridor.
  • C. formerLineName chosen
    Indicates that the object is a previous or former name by which the referenced line was known.
  • D. линия
    Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
  • E. lineHistorically
    Indicates that a line or route has existed or operated during a specific historical period or context.
  • 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_69f76ef20bb0819088b5b6ceecb0b8fc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc36ce1f88190a7fa1656b714e107 completed May 6, 2026, 10:40 p.m.
PD Predicate disambiguation batch_69fbbd166a488190b1bf9316b0790801 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:20 p.m.