Triple

T14738938
Position Surface form Disambiguated ID Type / Status
Subject Mansa Sakura E346291 entity
Predicate hasTitle P38 FINISHED
Object Mansa E353705 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: Mansa | Statement: [Mansa Sakura, hasTitle, Mansa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mansa
Context triple: [Mansa Sakura, hasTitle, Mansa]
  • A. Mansa chosen
    Mansa was the royal title used by the rulers of the Mali Empire, most famously borne by Mansa Musa, one of the wealthiest and most influential monarchs in history.
  • B. Mansa
    Mansa is a city in the Malwa region of Punjab, India, known primarily as an agricultural and cotton-growing center.
  • C. Mansa Mata
    Mansa Mata is a personal name that incorporates "Mata" as a suffix, likely reflecting cultural or linguistic naming traditions.
  • D. Mansa Uli
    Mansa Uli was a ruler of the Mali Empire and the son of its founder Sundiata Keita, known for consolidating and expanding the empire after his father's reign.
  • E. Mansa Qasa
    Mansa Qasa was a relatively obscure ruler of the Mali Empire who briefly held the throne following the reign of the powerful emperor Mansa Souleyman in the 14th century.
  • 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_69d822e6f1c88190bc494d491a907114 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec73264848190be23c5f0260cbe13 completed April 14, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69feb7d279708190a54a56c0b80be10a completed May 9, 2026, 4:28 a.m.
Created at: April 10, 2026, 1:29 a.m.