Triple

T9352357
Position Surface form Disambiguated ID Type / Status
Subject Bura-Pabir E225048 entity
Predicate hasAlternativeName P39 FINISHED
Object Pabir E793220 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: Pabir | Statement: [Bura-Pabir, hasAlternativeName, Pabir]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pabir
Context triple: [Bura-Pabir, hasAlternativeName, Pabir]
  • A. Pabir chosen
    The Pabir are an ethnic group of West Africa, closely associated with the Bura people and primarily found in northeastern Nigeria.
  • B. Pandua
    Pandua is a historic city in present-day West Bengal, India, that served as an important political and cultural center during the medieval Bengal Sultanate.
  • C. Khowai
    Khowai is a town in the northeastern Indian state of Tripura, known as an administrative and commercial center for the surrounding region.
  • D. Gogra
    Gogra is an alternative name for Kauriala, a locality whose identity is primarily tied to this regional designation.
  • E. Surkhob
    Surkhob is the historical name of a major river in Central Asia that forms part of what is now known as the Vakhsh River in Tajikistan.
  • 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_69ca842abfd48190949d71c3b86eeba8 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd4f93a9848190ad2ae24f2aa607d2 completed April 1, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0f3d248a88190b7d17af66e2903c5 completed April 4, 2026, 11:19 a.m.
Created at: March 30, 2026, 7:41 p.m.