Triple

T26496504
Position Surface form Disambiguated ID Type / Status
Subject Northern Boyacá Province E669295 entity
Predicate hasBorderWithinDepartment P144171 FINISHED
Object Central Boyacá Province 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: Central Boyacá Province | Statement: [Northern Boyacá Province, hasBorderWithinDepartment, Central Boyacá Province]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderWithinDepartment
Context triple: [Northern Boyacá Province, hasBorderWithinDepartment, Central Boyacá Province]
  • A. hasBorderWithinCountry
    Indicates that one region or area shares an internal boundary with another region or area within the same country.
  • B. sharesBorderWithDepartment chosen
    Indicates that one administrative department directly borders or touches the territorial boundary of another department.
  • C. hasBorderAgencyPresence
    Indicates that a border control or customs agency operates or maintains an official presence at a specified border location or crossing.
  • D. isBorderDistrict
    Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
  • E. hasBorderRelation
    Indicates that one entity shares a boundary or border with 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 27, 2026, 1:09 a.m.