Triple
T19646331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zayn |
E471680
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Zayn al-Din |
—
|
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: Zayn al-Din | Statement: [Zayn, relatedName, Zayn al-Din]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zayn al-Din Context triple: [Zayn, relatedName, Zayn al-Din]
-
A.
Zayn al-Din
chosen
Zayn al-Din is a male given name of Arabic origin, commonly used in Muslim communities and often associated with religious or scholarly figures.
-
B.
Ghias ad-Din
Ghias ad-Din was a Muslim prince, likely of Khwarazmian origin, who became consort to Queen Rusudan of Georgia through a politically motivated royal marriage.
-
C.
Alāʾ al-Dīn
Alāʾ al-Dīn was the honorific regnal name of Kayqubad II, a 13th-century Seljuk sultan of Rum.
-
D.
Izz al-Din Masud
Izz al-Din Masud was a medieval Muslim ruler of the Zengid dynasty who governed parts of northern Iraq and Syria during the 12th century.
-
E.
Burhan al-Din
Burhan al-Din is an Islamic honorific title meaning "Proof of the Religion," traditionally bestowed on distinguished religious scholars and jurists.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641250e108190a707452fefc87041 |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.