Triple

T28176365
Position Surface form Disambiguated ID Type / Status
Subject Ploiești Nord railway station E715599 entity
Predicate connectsToCityBy P193295 FINISHED
Object urban public transport in Ploiești 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: urban public transport in Ploiești | Statement: [Ploiești Nord railway station, connectsToCityBy, urban public transport in Ploiești]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsToCityBy
Context triple: [Ploiești Nord railway station, connectsToCityBy, urban public transport in Ploiești]
  • A. connectsCityTo
    Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
  • B. connectsCityIndirectly
    Indicates that one location is linked to a city through one or more intermediate locations or routes, rather than by a direct connection.
  • C. connectsCity
    Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
  • D. connectsMajorCity
    Indicates that one entity serves as a link or route providing direct connection to a major city.
  • E. connectsRegionalCity
    Indicates a relationship where one entity serves as a link or transport route between a regional city and another location.
  • 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_69efd6b340f0819095680e15dcdc1830 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69fd4129a8848190a5002150278ac689 completed May 8, 2026, 1:49 a.m.
PD Predicate disambiguation batch_69fd3e0515ec8190937c7af71ebc3875 completed May 8, 2026, 1:36 a.m.
PDg Predicate description generation batch_69fd4128ed908190837ec9936774a1cf completed May 8, 2026, 1:49 a.m.
Created at: April 27, 2026, 10:16 p.m.