Triple

T20601138
Position Surface form Disambiguated ID Type / Status
Subject Kresna E506181 entity
Predicate hasNearbyBorderDirection P115093 FINISHED
Object north of the Greek border 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: north of the Greek border | Statement: [Kresna, hasNearbyBorderDirection, north of the Greek border]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyBorderDirection
Context triple: [Kresna, hasNearbyBorderDirection, north of the Greek border]
  • A. hasNearbyBoundary
    Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of another entity.
  • B. hasBorderDirection
    Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
  • C. nearBorderDirection chosen
    Indicates that one entity is located close to a border or boundary in a specified directional orientation relative to that border.
  • D. hasNearbyCountyBorder
    Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
  • E. hasNeighbouringUnit
    Indicates that one unit is directly adjacent to and shares a boundary or side with another unit.
  • 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_69e0b4ba6ae88190af871e1f9522c704 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aa1ffd088190adeacb9fe4907530 completed April 20, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69e59fffe1748190825e4eaa90340631 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:41 a.m.