Triple

T14820155
Position Surface form Disambiguated ID Type / Status
Subject Lindi Region E348427 entity
Predicate borderedBy P224 FINISHED
Object Ruvuma Region E544796 NE 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: Ruvuma Region | Statement: [Lindi Region, borderedBy, Ruvuma Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruvuma Region
Context triple: [Lindi Region, borderedBy, Ruvuma Region]
  • A. Ruvuma Region chosen
    Ruvuma Region is a largely rural administrative area in southern Tanzania known for its wildlife, forests, and proximity to major conservation areas.
  • B. Lindi Region
    Lindi Region is a coastal administrative region in southern Tanzania known for its historical Swahili settlements and Indian Ocean shoreline.
  • C. Vumba region
    The Vumba region is a scenic highland area in eastern Zimbabwe known for its lush forests, cool misty climate, and rich biodiversity, attracting nature lovers and tourists.
  • D. Mafinga region
    Mafinga Region is an administrative area in Tanzania that includes Mafinga Central and surrounding localities.
  • E. Manzini Region
    Manzini Region is one of Eswatini’s four administrative regions, centrally located and home to the country’s largest urban and commercial center, Manzini city.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decfe4cf38819090f25ef045351d5d completed April 14, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69fea5a421e88190a7cd359209ae2818 completed May 9, 2026, 3:10 a.m.
Created at: April 10, 2026, 1:50 a.m.