Triple

T22214536
Position Surface form Disambiguated ID Type / Status
Subject Ragama E549039 entity
Predicate hasRailJunctionRole P14468 FINISHED
Object junction for trains between Colombo and Puttalam 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: junction for trains between Colombo and Puttalam | Statement: [Ragama, hasRailJunctionRole, junction for trains between Colombo and Puttalam]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRailJunctionRole
Context triple: [Ragama, hasRailJunctionRole, junction for trains between Colombo and Puttalam]
  • A. railwayJunctionFor chosen
    Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
  • B. hasRailInterchangeFunction
    Indicates that something serves as a location or facility where rail lines connect or intersect, allowing passengers or goods to transfer between them.
  • C. hasJunctionWith
    Indicates that one entity meets or intersects with another at a shared junction point.
  • D. connectsToRailStation
    Indicates that one entity has a direct link, route, or access connection to a rail station.
  • E. connectsToRailwayNetwork
    Indicates that one entity is physically or functionally linked to a railway network, allowing access or transfer between them.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b8b13f8819099ed8bebbfea3bc8 completed April 28, 2026, 9:50 p.m.
PD Predicate disambiguation batch_69e71b4dcc408190a30429fb08fcf39e completed April 21, 2026, 6:38 a.m.
Created at: April 16, 2026, 8:37 p.m.