Triple

T35229447
Position Surface form Disambiguated ID Type / Status
Subject Serbian community in Bulgaria E1017189 entity
Predicate sharesBorderAcross P202115 FINISHED
Object Serbia 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: Serbia | Statement: [Serbian community in Bulgaria, sharesBorderAcross, Serbia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharesBorderAcross
Context triple: [Serbian community in Bulgaria, sharesBorderAcross, Serbia]
  • A. shareBorderBetween
    Indicates that two geographic or political entities have a common boundary where their territories directly touch.
  • B. shareBorderAgreement
    Indicates that two entities have a formally recognized agreement concerning their shared border.
  • C. sharesBorderWithConceptually
    Indicates that one entity is conceptually adjacent to another, such that their ideas, domains, or categories touch or overlap like neighboring regions on a map.
  • D. sharesBorderOperationsWith
    Indicates that two entities coordinate or conduct joint operational activities in areas where their borders or jurisdictions meet.
  • E. shareNotableBorderRegion
    Indicates that two entities share a common border in a region that is particularly significant or notable (e.g., historically, politically, or geographically).
  • 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_69f76de12e4c8190bc46b71a32858356 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_6a005247dba08190acadf962bcefe4a0 completed May 10, 2026, 9:39 a.m.
PD Predicate disambiguation batch_6a00519029848190a234358dfba45084 completed May 10, 2026, 9:36 a.m.
PDg Predicate description generation batch_6a00524723408190b0294e87e5cf7715 completed May 10, 2026, 9:39 a.m.
Created at: May 3, 2026, 4:02 p.m.