Triple

T17425933
Position Surface form Disambiguated ID Type / Status
Subject Berezhany Raion E423736 entity
Predicate borderedByAdministrativeUnit P120977 FINISHED
Object neighboring raions of Ternopil Oblast 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: neighboring raions of Ternopil Oblast | Statement: [Berezhany Raion, borderedByAdministrativeUnit, neighboring raions of Ternopil Oblast]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderedByAdministrativeUnit
Context triple: [Berezhany Raion, borderedByAdministrativeUnit, neighboring raions of Ternopil Oblast]
  • A. borderedBy
    Indicates that one entity shares a common boundary or edge with another entity.
  • B. borderingAdministrativeTerritorialEntity chosen
    Indicates that one administrative territorial entity shares a common boundary with another administrative territorial entity.
  • C. borderingUnitType
    Indicates that one unit is adjacent to another unit of a specified type along a shared boundary.
  • D. hasBorderWithNonSovereignEntity
    Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
  • E. provinceBordering
    Indicates that two provinces share a common boundary or border with each other.
  • 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e448fbfda88190be1c001d64289bf7 completed April 19, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69e3b030eac481909b8402719cc3102e completed April 18, 2026, 4:24 p.m.
Created at: April 10, 2026, 5:46 a.m.