Triple
T15914665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu al-Faiz |
E385938
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Fayzi |
E904200
|
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: Fayzi | Statement: [Abu al-Faiz, alsoKnownAs, Fayzi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fayzi Context triple: [Abu al-Faiz, alsoKnownAs, Fayzi]
-
A.
Fayiz
chosen
Fayiz is a masculine given name of Arabic origin, commonly used as a variant transliteration of the name Fayez.
-
B.
Faizi
Faizi was a renowned 16th-century Persian-language poet and scholar who served as one of the prominent intellectuals in the Mughal emperor Akbar’s court.
-
C.
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.
-
D.
Fahri
Fahri is a Turkish masculine given name commonly borne by notable figures in politics, arts, and public life.
-
E.
Zafar
Zafar was an important ancient South Arabian city that served as the political and cultural center of the Himyarite Kingdom in what is now Yemen.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1566216d481908dd6e3acaa26fd45 |
completed | April 16, 2026, 9:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb5a79b808190850fa9d327f7ef72 |
completed | May 9, 2026, 10:31 p.m. |
Created at: April 10, 2026, 4:52 a.m.