Triple
T5518631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Talal |
E144748
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | bin Abdullah |
E98654
|
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: bin Abdullah | Statement: [King Talal, familyName, bin Abdullah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: bin Abdullah Context triple: [King Talal, familyName, bin Abdullah]
-
A.
bin Abdullah
chosen
Bin Abdullah is an Arabic patronymic surname indicating descent from someone named Abdullah, commonly used across the Arab world.
-
B.
Abdullah
Abdullah is a common Arabic male given name, notably borne by King Abdullah II of Jordan.
-
C.
ibn Abdullah
Ibn Abdullah is an Arabic patronymic name meaning "son of Abdullah," commonly used across the Muslim world in historical and contemporary contexts.
-
D.
Mir Abdullah
Mir Abdullah was the son of the renowned Urdu and Persian poet Mir Taqi Mir, belonging to his literary and familial lineage in 18th-century India.
-
E.
Abu
Abu is Aladdin’s mischievous and loyal monkey sidekick in Disney’s animated Aladdin franchise.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f6eb604819092e9b2207dc741a9 |
completed | March 22, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027e1ed4c81908f670286556ced81 |
completed | March 22, 2026, 5:33 p.m. |
Created at: March 22, 2026, 3:33 p.m.