Triple
T8051242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humza Yousaf |
E187678
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Humza |
E176451
|
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: Humza | Statement: [Humza Yousaf, givenName, Humza]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Humza Context triple: [Humza Yousaf, givenName, Humza]
-
A.
Humera
Humera is a town in northwestern Ethiopia near the borders with Eritrea and Sudan, known for its strategic location and sesame production.
-
B.
Ilyas
Ilyas is the Arabic and Quranic form of the prophet Elijah, revered in Islamic tradition as a righteous messenger of God.
-
C.
Hamza
chosen
Hamza is a masculine given name of Arabic origin, commonly used in the Muslim world and among Arabic-speaking communities.
-
D.
Mirza
Mirza is a historical noble title of Persian and Central Asian origin, commonly borne by princes and high-ranking members of royal and aristocratic families.
-
E.
Khushal
Khushal is a male given name of Persian origin commonly used in South Asia, meaning "happy" or "prosperous."
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f799d1481909c91039941af0e34 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc571b737881909ae8eadcc7894223 |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 5:24 p.m.