Triple
T1615872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David |
E34716
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Dawud |
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: Dawud | Statement: [David, hasVariant, Dawud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dawud Context triple: [David, hasVariant, Dawud]
-
A.
Dawud
chosen
Dawud is a prophet and king in Islamic tradition, known for his wisdom, psalms, and just rule.
-
B.
Harun
Harun is the Islamic prophet Aaron, brother of Moses, revered for his prophethood and leadership among the Israelites.
-
C.
Eskandar
Eskandar is a Persian and Arabic form of the name Alexander, commonly used in historical and literary contexts to refer to Alexander the Great.
-
D.
Fereydun
Fereydun is a legendary hero and king in Persian mythology, best known from the Shahnameh for overthrowing the tyrant Zahhak and ushering in a just reign.
-
E.
Jamshid
Jamshid is a legendary king in Persian mythology, renowned for his long, prosperous reign and his central role in ancient Iranian cultural and epic traditions.
- 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_69ada96dc52c8190be0ace80c5eb4cf3 |
completed | March 8, 2026, 4:53 p.m. |
Created at: March 4, 2026, 7:28 p.m.