Triple

T18390044
Position Surface form Disambiguated ID Type / Status
Subject Bogotá–Tunja highway E449698 entity
Predicate connectsCapitalTo P60933 FINISHED
Object historic Andean city of Tunja 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: historic Andean city of Tunja | Statement: [Bogotá–Tunja highway, connectsCapitalTo, historic Andean city of Tunja]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: connectsCapitalTo
Context triple: [Bogotá–Tunja highway, connectsCapitalTo, historic Andean city of Tunja]
  • A. connectsCapital
    Indicates a relationship where one entity serves as the capital city that is officially linked to or associated with another entity, such as a country or region.
  • B. hasCapitalConnected
    Indicates that there is a direct connection or linkage between an entity and its capital city.
  • C. connectsCapitalToBorder
    Indicates a relationship where a capital city is linked or directly connected to a border location or boundary.
  • D. connectsCapitalWithRegion
    Indicates a relationship where a capital city is linked or associated with the larger region it belongs to.
  • E. connectsCityTo chosen
    Indicates a relationship in which a route, infrastructure, or link joins one city to another, enabling connection or interaction between them.
  • 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e518416bc48190a20fa66c43d545d9 completed April 19, 2026, 6 p.m.
PD Predicate disambiguation batch_69e44ff1f92c8190afbb8e85d12bf2a9 completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:46 a.m.