Triple

T30010188
Position Surface form Disambiguated ID Type / Status
Subject Allschwil–Bourgfelden border crossing E762434 entity
Predicate partOfSchengenAreaBorder P109217 FINISHED
Object true 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: true | Statement: [Allschwil–Bourgfelden border crossing, partOfSchengenAreaBorder, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partOfSchengenAreaBorder
Context triple: [Allschwil–Bourgfelden border crossing, partOfSchengenAreaBorder, true]
  • A. isSchengenExternalBorder chosen
    Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
  • B. EUInternalBorder
    Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
  • C. countryBorderFormsPartOf
    Indicates that a specific border segment is part of the overall boundary between two countries.
  • D. adjacentCountryBorderPost
    Indicates that a border post is located at or associated with the boundary between two adjacent countries.
  • E. isNATOExternalBorder
    Indicates that a location or boundary lies on the outer edge of NATO territory, forming part of NATO’s external border with non-member areas.
  • 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_69f2246b0c84819094f1250b6a02d277 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fed83b1d188190a318b0ad3003200a completed May 9, 2026, 6:46 a.m.
PD Predicate disambiguation batch_69fed78e03548190b6e6ad93ae8d131d completed May 9, 2026, 6:43 a.m.
Created at: April 29, 2026, 6:43 p.m.