Triple

T28758992
Position Surface form Disambiguated ID Type / Status
Subject Bab al-Salameh Border Crossing E731753 entity
Predicate oppositeSideFacility P169554 FINISHED
Object Öncüpınar Border Gate 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: Öncüpınar Border Gate | Statement: [Bab al-Salameh Border Crossing, oppositeSideFacility, Öncüpınar Border Gate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oppositeSideFacility
Context triple: [Bab al-Salameh Border Crossing, oppositeSideFacility, Öncüpınar Border Gate]
  • A. oppositeFacility chosen
    Indicates that one facility is located directly across from or facing another facility.
  • B. hasOppositeStationForOtherDirection
    Indicates that a station has a corresponding station used for travel in the opposite direction on the same route or line.
  • C. opposingLocation
    Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
  • D. situatedOnSideOf
    Indicates that one entity is located along or beside the lateral part or edge of another entity.
  • E. adjacentToInfrastructure
    Indicates that one entity is located directly next to or in immediate proximity to a piece of infrastructure.
  • 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_69f043ed68a881909e858a06bab7a247 completed April 28, 2026, 5:21 a.m.
NER Named-entity recognition batch_69f71996e1a48190ac59a1d66d7c44e8 completed May 3, 2026, 9:47 a.m.
PD Predicate disambiguation batch_69f71820c6c88190ab38b4fa626d22cc completed May 3, 2026, 9:40 a.m.
Created at: April 28, 2026, 6:11 a.m.