Triple
T18747157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homerite Kingdom |
E458433
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Zafar |
—
|
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: Zafar | Statement: [Homerite Kingdom, capital, Zafar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zafar Context triple: [Homerite Kingdom, capital, Zafar]
-
A.
Zafar
Zafar was the pen name of Bahadur Shah II, the last Mughal emperor of India and a noted Urdu poet.
-
B.
Zafar
chosen
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.
-
C.
Thadiq
Thadiq is a town in central Saudi Arabia known for its traditional architecture and location within the Riyadh administrative region.
-
D.
Asif
Asif is a common male given name used in South Asian and Middle Eastern cultures, notably borne by Pakistani politician Asif Ali Zardari.
-
E.
Zafar Saifullah
Zafar Saifullah was a senior Indian civil servant who served as Cabinet Secretary and held several key administrative positions in the Government of India.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e576936cf08190b3c0d2f4e8a616fc |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 10, 2026, 11:51 a.m.