Triple

T4099320
Position Surface form Disambiguated ID Type / Status
Subject Heiligenkreuz–Rábafüzes border crossing E87899 entity
Predicate hasBorderCheckpointType P14206 FINISHED
Object road 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 checkpoint | Statement: [Heiligenkreuz–Rábafüzes border crossing, hasBorderCheckpointType, road checkpoint]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderCheckpointType
Context triple: [Heiligenkreuz–Rábafüzes border crossing, hasBorderCheckpointType, road checkpoint]
  • A. hasBorderFacilityType chosen
    Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
  • B. hasBorderTerminus
    Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
  • C. hasBorderRole
    Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
  • D. hasBoundaryType
    Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
  • E. hasBorderDirection
    Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
  • 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_69aed94564cc8190a9c1457daedb6e7f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefd0d9c508190b8aedf83f3310513 completed March 9, 2026, 5:02 p.m.
PD Predicate disambiguation batch_69aef90b2ef08190ae84febfd69dd48b completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:40 p.m.