Triple

T5156959
Position Surface form Disambiguated ID Type / Status
Subject Hüma Hatun E116333 entity
Predicate hasTitle P38 FINISHED
Object Hatun E447353 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: Hatun | Statement: [Hüma Hatun, hasTitle, Hatun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hatun
Context triple: [Hüma Hatun, hasTitle, Hatun]
  • A. Hatun chosen
    Hatun is a historical Turkish honorific title traditionally used for noblewomen or ladies of high social status in Turkic and Ottoman societies.
  • B. Harauti
    Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
  • C. Hunza
    Hunza is a mountainous valley and popular tourist destination in northern Pakistan, renowned for its dramatic Karakoram scenery and traditionally long-lived local population.
  • D. Hunza
    Hunza was the principal city and political center of the Zaque rulers within the pre-Columbian Muisca Confederation in what is now central Colombia.
  • E. Hachuamish
    Hachuamish is a traditional clan or band within the Duwamish people, an Indigenous Coast Salish group native to the Seattle area of Washington State.
  • 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_69bd445d94788190b72e2cc563120995 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7902fbe48190abb58cb0b2b2b62d completed March 20, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bed0168a648190a470507802aa8934 completed March 21, 2026, 5:06 p.m.
Created at: March 20, 2026, 1:44 p.m.