Triple

T8362748
Position Surface form Disambiguated ID Type / Status
Subject Yeonsan Station E197048 entity
Predicate publicTransportNetworkRole P29465 FINISHED
Object interchange node 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: interchange node | Statement: [Yeonsan Station, publicTransportNetworkRole, interchange node]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicTransportNetworkRole
Context triple: [Yeonsan Station, publicTransportNetworkRole, interchange node]
  • A. hasPublicTransitRole chosen
    Indicates that an entity holds a specific functional role or responsibility within a public transit system.
  • B. transportationRole
    Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
  • C. publicTransportAuthorityRelation
    Indicates that one entity serves as the public transport authority responsible for overseeing, regulating, or managing public transportation services related to another entity.
  • D. publicTransportZone
    Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
  • E. publicTransportAuthority
    Indicates that one entity serves as the governing or managing authority responsible for overseeing public transportation services related to another entity.
  • 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_69ca82f2dbe48190aba982e75a0d94de completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb80768b208190a5f6c9e6cb6e7f30 completed March 31, 2026, 8:06 a.m.
PD Predicate disambiguation batch_69cb70ca25548190b0f90c5384e3fb3c completed March 31, 2026, 6:59 a.m.
Created at: March 30, 2026, 6 p.m.