Triple

T23117808
Position Surface form Disambiguated ID Type / Status
Subject Mahperi Hatun E576805 entity
Predicate hasTitle P38 FINISHED
Object Hatun NE NERFINISHED

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: [Mahperi Hatun, hasTitle, Hatun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hatun
Context triple: [Mahperi 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. Hauya
    Hauya is a small genus of flowering plants in the evening primrose family, native to mountainous regions of Central and South America.
  • C. Harauti
    Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
  • 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. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245f6c2e881909a228fdcfeb7c7d3 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e4dd7d8819087cc50b2dc94798e completed April 29, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:59 p.m.