Triple

T15903105
Position Surface form Disambiguated ID Type / Status
Subject Tabodwe E385639 entity
Predicate follows P134 FINISHED
Object Pyatho E385638 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: Pyatho | Statement: [Tabodwe, follows, Pyatho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyatho
Context triple: [Tabodwe, follows, Pyatho]
  • A. Pyatho chosen
    Pyatho is one of the traditional months in the Burmese lunisolar calendar, used in Myanmar for cultural and religious observances.
  • B. Egoli
    Egoli is a common nickname for Johannesburg, South Africa’s major economic hub often referred to as the "City of Gold."
  • C. Ulundi
    Ulundi is a historic town in KwaZulu-Natal, South Africa, best known as the former royal and political center of the Zulu Kingdom and the site of key events in the Anglo-Zulu War.
  • D. Witbank
    Witbank is a South African coal-mining city in Mpumalanga province, now officially known as Emalahleni.
  • E. Pretoria, South Africa
    Pretoria, South Africa is one of the country’s three capital cities, serving as the administrative capital and a major center for government, education, and culture.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1563e79608190a1fdfe6265817616 completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffc3bb7d608190babbea74a9ca9f4c completed May 9, 2026, 11:31 p.m.
Created at: April 10, 2026, 4:52 a.m.