Triple

T31936284
Position Surface form Disambiguated ID Type / Status
Subject TRC E815395 entity
Predicate connectsToCountryByRail P182398 FINISHED
Object Burundi NE NERFINISHED

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: Burundi | Statement: [TRC, connectsToCountryByRail, Burundi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsToCountryByRail
Context triple: [TRC, connectsToCountryByRail, Burundi]
  • A. hasBorderRailConnectionWith chosen
    Indicates that two places are directly connected to each other by a cross-border railway line or service.
  • B. hasPassengerRailConnection
    Indicates that there exists a passenger rail service linking one location or transport node to another.
  • C. isMainInternationalRailStopOf
    Indicates that a location serves as the primary international railway stop or station for a given area, route, or settlement.
  • D. railNetworkCountry
    Indicates that a rail network is located within, or primarily serves, a specific country.
  • E. providesRailConnectionsWithin
    Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
  • 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_69f348f3035c81908558e2339955abb3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69feabcda59481908f2bc13b46fcced1 completed May 9, 2026, 3:36 a.m.
PD Predicate disambiguation batch_69feaabd63f88190b30dcf6dd2ea39d1 completed May 9, 2026, 3:32 a.m.
Created at: May 1, 2026, 12:05 a.m.