Triple
T1615871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David |
E34716
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Daud |
E142700
|
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: Daud | Statement: [David, hasVariant, Daud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Daud Context triple: [David, hasVariant, Daud]
-
A.
Salim
Salim was the birth name of Jahangir, the fourth Mughal emperor of India known for his patronage of the arts and consolidation of the empire.
-
B.
Ilyas
Ilyas is the Arabic and Quranic form of the prophet Elijah, revered in Islamic tradition as a righteous messenger of God.
-
C.
Mirza
Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
-
D.
Dawud
chosen
Dawud is a prophet and king in Islamic tradition, known for his wisdom, psalms, and just rule.
-
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9099049e0819099763ecb09fb4f57 |
completed | March 5, 2026, 4:41 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51cd2e54819086924378792eb2e3 |
completed | March 8, 2026, 10:39 a.m. |
Created at: March 4, 2026, 7:28 p.m.