Triple
T21596418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayah bint Faisal |
E532911
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | bint Faisal |
—
|
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: bint Faisal | Statement: [Ayah bint Faisal, familyName, bint Faisal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: bint Faisal Context triple: [Ayah bint Faisal, familyName, bint Faisal]
-
A.
bint Faisal
chosen
bint Faisal is a Jordanian royal family surname borne by several princesses and princes descended from King Faisal.
-
B.
bin Faisal
bin Faisal is an Arabic patronymic family name associated with the Hashemite royal family, notably borne by figures such as Ghazi bin Faisal, former king of Iraq.
-
C.
Faisal
Faisal is a male given name of Arabic origin, historically borne by several notable Middle Eastern leaders and royals.
-
D.
Fazl
Fazl is the given name of Fazl-e-Haq Khairabadi, a 19th-century Indian Islamic scholar, philosopher, and prominent figure in the Indian Rebellion of 1857.
-
E.
Azeem Edin Bashir Al Bakir
Azeem Edin Bashir Al Bakir is an individual known primarily as a name variant or extended form of the name Azeem.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae15a7c819081627450ae726b0b |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 16, 2026, 6:32 p.m.