Triple

T20100052
Position Surface form Disambiguated ID Type / Status
Subject Shenyang–Dandong Railway E496508 entity
Predicate hasEndpointFunction P49042 FINISHED
Object border access at Dandong 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: border access at Dandong | Statement: [Shenyang–Dandong Railway, hasEndpointFunction, border access at Dandong]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEndpointFunction
Context triple: [Shenyang–Dandong Railway, hasEndpointFunction, border access at Dandong]
  • A. hasEndpointType
    Indicates that an entity has a specific type or classification assigned to one of its endpoints.
  • B. hasServiceFunction
    Indicates that an entity performs, provides, or is responsible for a particular service-related function or role.
  • C. hasHubFunction
    Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
  • D. hasTerminalFunction chosen
    Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
  • E. hasJunctionFunction
    Indicates that one entity serves as a junction or connecting function for another entity within a system or structure.
  • 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666f2298819089659f13556ca305 completed April 20, 2026, 5:46 p.m.
PD Predicate disambiguation batch_69e54cf788188190a46cc49c9ce7617f completed April 19, 2026, 9:45 p.m.
Created at: April 11, 2026, 11:26 p.m.