Triple

T28482957
Position Surface form Disambiguated ID Type / Status
Subject Nopo E720743 entity
Predicate hasIntercityBusConnectionsTo P193295 FINISHED
Object other cities in South Korea 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: other cities in South Korea | Statement: [Nopo, hasIntercityBusConnectionsTo, other cities in South Korea]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIntercityBusConnectionsTo
Context triple: [Nopo, hasIntercityBusConnectionsTo, other cities in South Korea]
  • A. hasPassengerRailConnection
    Indicates that there exists a passenger rail service linking one location or transport node to another.
  • B. connectsToCityBy chosen
    Indicates that one entity is linked or has a direct connection to a specific city, such as through infrastructure, routes, or established relations.
  • C. providesRailConnectionsWithin
    Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
  • D. hasNightTrainService
    Indicates that a transportation route or station is served by trains that operate during nighttime hours.
  • E. hasPublicTransportConnection
    Indicates that there is an available public transportation link or service connecting 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_69f01a5a47148190b0a7e111bc432e0a completed April 28, 2026, 2:24 a.m.
NER Named-entity recognition batch_69fda94697c4819081291967202248be completed May 8, 2026, 9:13 a.m.
PD Predicate disambiguation batch_69fda5973fcc8190a57daef31fb70a49 completed May 8, 2026, 8:57 a.m.
Created at: April 28, 2026, 2:56 a.m.