Triple

T23219404
Position Surface form Disambiguated ID Type / Status
Subject Inharrime District E580844 entity
Predicate borders P224 FINISHED
Object Homoine District 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: Homoine District | Statement: [Inharrime District, borders, Homoine District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Homoine District
Context triple: [Inharrime District, borders, Homoine District]
  • A. Homoine District chosen
    Homoine District is an administrative district located in Inhambane Province in southern Mozambique.
  • B. Anci District
    Anci District is an administrative urban district within the prefecture-level city of Langfang in Hebei Province, northern China.
  • C. Yanatile District
    Yanatile District is an administrative district located within Calca Province in Peru's Cusco Region, known for its Andean landscapes and rural communities.
  • D. Rezina District
    Rezina District is an administrative region in eastern Moldova known for its location along the Răut River and its mix of rural communities and historical sites.
  • E. Butebo District
    Butebo District is an administrative district in eastern Uganda known for its predominantly rural communities and agriculture-based economy.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f191675de48190858907872a065c56 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.