Triple
T6984172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir Fateh Ali Khan Talpur |
E161920
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Talpur |
E604072
|
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: Talpur | Statement: [Mir Fateh Ali Khan Talpur, familyName, Talpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Talpur Context triple: [Mir Fateh Ali Khan Talpur, familyName, Talpur]
-
A.
Talpur
chosen
Talpur is a Baloch royal dynasty and clan historically known for ruling parts of Sindh in present-day Pakistan during the 18th and 19th centuries.
-
B.
Sachal
Sachal is the honorific name of Sachal Sarmast, an 18th–19th century Sindhi Sufi poet and mystic renowned for his multilingual poetry and message of spiritual unity.
-
C.
Shamardal
Shamardal was a champion Thoroughbred racehorse and highly influential sire known for producing multiple Group 1 winners in Europe.
-
D.
Miranshah
Miranshah was a son of the Turco-Mongol conqueror Timur (Tamerlane) who served as one of his key governors and military commanders in the Timurid Empire.
-
E.
Hyder
Hyder is a surname of South Asian origin commonly found among Muslim families, including that of the fictional character Sufiya Zinobia.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db90e9108190a7aedeef1fb17eb4 |
completed | March 27, 2026, 7:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761c671588190a4e7b5c26cdfe6ba |
completed | March 28, 2026, 5:06 a.m. |
Created at: March 27, 2026, 2:31 p.m.