Triple

T14852873
Position Surface form Disambiguated ID Type / Status
Subject A3 E349273 entity
Predicate terminus P388 FINISHED
Object Chirundu E672891 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: Chirundu | Statement: [A3, terminus, Chirundu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chirundu
Context triple: [A3, terminus, Chirundu]
  • A. Chirundu chosen
    Chirundu is a border town in northern Zimbabwe situated on the Zambezi River, serving as a key crossing point between Zimbabwe and Zambia.
  • B. Luchazi
    Luchazi is a Bantu language spoken primarily by the Luchazi people in eastern Angola and neighboring regions.
  • C. Mankwe
    Mankwe is a locality in South Africa, historically part of the former Bophuthatswana homeland in the North West Province.
  • D. Poruba
    Poruba is a large residential and administrative district of the city of Ostrava in the Czech Republic, known for its distinctive socialist realist architecture and extensive green spaces.
  • E. Mberengwa
    Mberengwa is a rural district and growth point in Zimbabwe known for its mining activities and location in the southern part of the Midlands Province.
  • 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_69d822ed7e1881909b90fca143ad7e34 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded441e70881909bbf62b66d932aff completed April 14, 2026, 11:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe72a87dd88190b0f0c3b9b625a7e6 completed May 8, 2026, 11:32 p.m.
Created at: April 10, 2026, 1:54 a.m.