Triple
T23308914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibatullah Akhundzada |
E590527
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hibatullah |
—
|
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: Hibatullah | Statement: [Hibatullah Akhundzada, givenName, Hibatullah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hibatullah Context triple: [Hibatullah Akhundzada, givenName, Hibatullah]
-
A.
Hibatullah
chosen
Hibatullah is the given name of Hibatullah Akhundzada, the reclusive supreme leader of the Taliban in Afghanistan.
-
B.
Azizullah
Azizullah is a male given name of Arabic origin, commonly used in Muslim communities and meaning "dear to God" or "beloved of Allah."
-
C.
Khalilullah
Khalilullah is an honorific title meaning "Friend of God," traditionally associated with the prophet Ibrahim (Abraham) in Islamic tradition.
-
D.
Ubaydullah
Ubaydullah is an Arabic male given name historically borne by several early Islamic figures.
-
E.
Nasrullah
Nasrullah was a highly influential Thoroughbred racehorse and sire whose bloodline has shaped modern flat and National Hunt racing.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19729f7a4819092a1d24415b3df7a |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:05 p.m.