Triple
T16387707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azad Rao Khan |
E397965
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Azad |
E136876
|
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: Azad | Statement: [Azad Rao Khan, givenName, Azad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Azad Context triple: [Azad Rao Khan, givenName, Azad]
-
A.
Azad
chosen
Azad is the revolutionary alias of Chandrasekhar Azad, a prominent Indian freedom fighter who played a key role in the struggle against British colonial rule.
-
B.
Abdi
Abdi is a masculine given name of Arabic origin commonly used in various Muslim-majority cultures.
-
C.
Mohammadzai
Mohammadzai is a prominent Pashtun tribal clan from Afghanistan historically associated with the Barakzai dynasty and rulers such as Emir Dost Mohammad Khan.
-
D.
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.
-
E.
Zafar
Zafar was the pen name of Bahadur Shah II, the last Mughal emperor of India and a noted Urdu poet.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e3263e1534819081a6bf5006c611c5 |
completed | April 18, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00356ed47c819085aaf101459dd55c |
completed | May 10, 2026, 7:36 a.m. |
Created at: April 10, 2026, 5:08 a.m.