Triple
T4702069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdus |
E104296
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Abdul |
E104296
|
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: Abdul | Statement: [Abdus, hasVariantForm, Abdul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abdul Context triple: [Abdus, hasVariantForm, Abdul]
-
A.
Abdus
chosen
Abdus is a given name most notably borne by Abdus Salam, the Pakistani theoretical physicist and Nobel laureate.
-
B.
Habib
Habib is a masculine given name of Arabic origin commonly used in North Africa and the Middle East.
-
C.
Omar
Omar is a masculine given name of Arabic origin meaning "flourishing" or "long-lived," borne by numerous historical and contemporary figures worldwide.
-
D.
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).
-
E.
Hussain
Hussain is a common given name and surname of Arabic origin, widely used in Muslim communities around the world.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd63cec7988190b5f1d04d4f95314a |
completed | March 20, 2026, 3:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be39dd7d9c8190912044c8616cf8a0 |
completed | March 21, 2026, 6:25 a.m. |
Created at: March 20, 2026, 1:17 p.m.