Triple
T13297003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zayd ibn al-Hasan |
E316710
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Zayd |
E1019692
|
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: Zayd | Statement: [Zayd ibn al-Hasan, givenName, Zayd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zayd Context triple: [Zayd ibn al-Hasan, givenName, Zayd]
-
A.
Zayd
chosen
Zayd is a male given name of Arabic origin commonly used in the Muslim world.
-
B.
Azzam
Azzam is a masculine given name of Arabic origin, commonly used in the Middle East and among Arabic-speaking communities.
-
C.
Zayd ibn al-Hasan
Zayd ibn al-Hasan was a descendant of the Prophet Muhammad through his father Hasan ibn Ali and a member of the early Islamic nobility of the Prophet’s family (Ahl al-Bayt).
-
D.
Zakariya
Zakariya is a revered prophet in Islamic and Christian traditions, known as the father of Prophet Yahya (John the Baptist).
-
E.
Yahya
Yahya is the Islamic prophet identified with John the Baptist, revered for his piety, asceticism, and role in heralding the coming of Prophet Isa (Jesus).
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990a2f2708190a8f2aa7e7c0b92d2 |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716dad3648190bf360955fbdfb2f0 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:28 p.m.