Triple

T20368617
Position Surface form Disambiguated ID Type / Status
Subject Kulata–Promachonas border crossing E496984 entity
Predicate roadCheckpointFor P139875 FINISHED
Object international road traffic 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: international road traffic | Statement: [Kulata–Promachonas border crossing, roadCheckpointFor, international road traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roadCheckpointFor
Context triple: [Kulata–Promachonas border crossing, roadCheckpointFor, international road traffic]
  • A. roadTraverses
    Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
  • B. roadTerminusOf
    Indicates that a road ends at, or has its terminal point at, the referenced location or route.
  • C. roadFeature
    Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
  • D. locatedOnRouteTo
    Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
  • E. startsAtRoad
    Indicates that something begins or originates at a specific road or roadway location.
  • F. None of above. chosen

Provenance (4 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_69e0b4a4f9b081908a5a021919c21ccb completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678734b188190bb2c5863023f9f8c completed April 20, 2026, 7:03 p.m.
PD Predicate disambiguation batch_69e57648be3c81908256838228cabf5c completed April 20, 2026, 12:41 a.m.
PDg Predicate description generation batch_69e58d7481508190a87c8b88f9df9879 completed April 20, 2026, 2:20 a.m.
Created at: April 16, 2026, 11:26 a.m.