Triple

T27100036
Position Surface form Disambiguated ID Type / Status
Subject Krasnodar trolleybus E686413 entity
Predicate isRailBound P101263 FINISHED
Object no 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: no | Statement: [Krasnodar trolleybus, isRailBound, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isRailBound
Context triple: [Krasnodar trolleybus, isRailBound, no]
  • A. isRailwayIn
    Indicates that a railway is located within or passes through a specified geographic or administrative area.
  • B. hasRail chosen
    Indicates that something is equipped with, includes, or is connected to a rail or rail system.
  • C. isOnRailway
    Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
  • D. isRailServiceOf
    Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
  • E. hasRailRoute
    Indicates that there exists a rail-based transportation route or connection between the related 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_69ef1489f8b481908e24a1985982bd26 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f623b54dfc8190b9294ac42f940415 completed May 2, 2026, 4:17 p.m.
PD Predicate disambiguation batch_69f61b40f02081909bd9c3ea73249163 completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 8:47 a.m.