Triple

T31790564
Position Surface form Disambiguated ID Type / Status
Subject Malmbanan E811450 entity
Predicate hasCrossBorderSection P173239 FINISHED
Object Sweden–Norway border 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: Sweden–Norway border | Statement: [Malmbanan, hasCrossBorderSection, Sweden–Norway border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderSection
Context triple: [Malmbanan, hasCrossBorderSection, Sweden–Norway border]
  • A. hasCrossBorderArea
    Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
  • B. crossBorderSection chosen
    Indicates a section or segment that extends across or passes from one jurisdiction, region, or country into another.
  • C. haveCrossBorderCorridor
    Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
  • D. hasCrossBorderCenter
    Indicates that an entity operates or is associated with a center whose activities, services, or scope extend across national borders.
  • E. hasCrossBorderInteraction
    Indicates that there is an interaction, activity, or relationship occurring between entities located in different countries or jurisdictions.
  • 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_69f348e60748819082dcaa7792659803 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f7886be6d8819095ec62e4f2cee858 completed May 3, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69f7841440f48190b4346c08855951d2 completed May 3, 2026, 5:21 p.m.
Created at: April 30, 2026, 11:39 p.m.