Triple
T7055379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdülmecid II |
E164074
|
entity |
| Predicate | mother |
P120
|
FINISHED |
| Object | Hayranidil Kadın |
E473318
|
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: Hayranidil Kadın | Statement: [Abdülmecid II, mother, Hayranidil Kadın]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hayranidil Kadın Context triple: [Abdülmecid II, mother, Hayranidil Kadın]
-
A.
Hayranidil Kadın
chosen
Hayranidil Kadın was a consort of Ottoman Sultan Abdülaziz and the mother of Sultan Mehmed V Reşad.
-
B.
Tirimüjgan Kadın
Tirimüjgan Kadın was an Ottoman consort of Sultan Abdulmejid I and the mother of Sultan Abdul Hamid II.
-
C.
Peyveste Hanım
Peyveste Hanım was one of the consorts of Ottoman Sultan Abdul Hamid II and a member of the late Ottoman imperial harem.
-
D.
Edadil Kadın
Edadil Kadın was a consort of Ottoman Sultan Abdülaziz and a member of the 19th-century Ottoman imperial harem.
-
E.
Khatun
Khatun is a historical title used in Turkic and Mongol societies for a noblewoman or queen, often the wife or female counterpart of a khan.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e267664c81909501feb12683a002 |
completed | March 27, 2026, 8:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7889ddd488190b1e55828909133eb |
completed | March 28, 2026, 7:51 a.m. |
Created at: March 27, 2026, 2:38 p.m.