Triple

T717194
Position Surface form Disambiguated ID Type / Status
Subject Basel–Saint-Louis crossing E14339 entity
Predicate hasBorderFunction P10963 FINISHED
Object road border checkpoint 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: road border checkpoint | Statement: [Basel–Saint-Louis crossing, hasBorderFunction, road border checkpoint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderFunction
Context triple: [Basel–Saint-Louis crossing, hasBorderFunction, road border checkpoint]
  • A. hasBorderCrossingFunction chosen
    Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
  • B. hasBorderLocality
    Indicates that one locality is situated along or adjacent to the border of another locality.
  • C. hasBorderFacilityType
    Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
  • D. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • E. hasBoundaryType
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • 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_69a4934a36e081909e7abef98b898a4e completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a57649dc8190bfdee2f9c0c90415 completed March 1, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69a4a4f38898819089d79bad4f4ff2d2 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.