Triple
T13574927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hassan |
E324255
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Murad Mirza |
E83120
|
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: Murad Mirza | Statement: [Hassan, sibling, Murad Mirza]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Murad Mirza Context triple: [Hassan, sibling, Murad Mirza]
-
A.
Murad Mirza
chosen
Murad Mirza was a Mughal prince of the 16th century, known as one of Emperor Akbar’s sons who held military commands but died relatively young.
-
B.
Murad Bey
Murad Bey was a prominent Mamluk military leader and ruler in late 18th-century Egypt who fiercely resisted Napoleon’s invasion.
-
C.
Murad
Murad is a masculine given name of Arabic origin commonly used in various Muslim-majority cultures.
-
D.
Murad I
Murad I was a 14th-century Ottoman sultan who significantly expanded Ottoman territories in the Balkans and Anatolia, laying key foundations for the empire’s rise.
-
E.
Ala ad-Din Muhammad II
Ala ad-Din Muhammad II was the Shah of the Khwarazmian Empire in the early 13th century, whose conflict with the Mongol Empire helped trigger the Mongol invasions of the Islamic world.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77f8bda0c81909afd4b9ef9605cd3 |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:48 p.m.