Triple

T28572625
Position Surface form Disambiguated ID Type / Status
Subject King of Burundi E723152 entity
Predicate hasCapitalConnection P138548 FINISHED
Object Gitega 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: Gitega | Statement: [King of Burundi, hasCapitalConnection, Gitega]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCapitalConnection
Context triple: [King of Burundi, hasCapitalConnection, Gitega]
  • A. hasCapitalConnected
    Indicates that there is a direct connection or linkage between an entity and its capital city.
  • B. hasCapitalLink chosen
    Indicates a relationship in which one entity is connected to another by being its capital (typically the capital city of a region, state, or country).
  • C. hasMetropolitanConnectionWith
    Indicates that there is a significant relationship or linkage between two entities based on shared or interacting metropolitan areas, such as through infrastructure, services, or regional integration.
  • D. regionCapitalConnected
    Indicates that a capital city is directly connected (e.g., by transport or infrastructure) to its surrounding region.
  • E. connectsCapitalWith
    Indicates a relationship where something serves as a link or route between a capital city and another place or 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_69f01d7e97708190ae9e77ee66a68abd completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69fce28d6c3081908bf76f5db63ecf68 completed May 7, 2026, 7:05 p.m.
PD Predicate disambiguation batch_69fce12d2f08819082134b5eb3db6a24 completed May 7, 2026, 6:59 p.m.
Created at: April 28, 2026, 4:10 a.m.