Triple
T15626097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultan Mehmood Chaudhry |
E375682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kashmiri politician |
C36429
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Kashmiri politician Context triple: [Sultan Mehmood Chaudhry, instanceOf, Kashmiri politician]
-
A.
Sindhi politician
A Sindhi politician is a public figure from the Sindhi community who engages in political activities, represents Sindhi interests, and participates in governance and policy-making at local, regional, or national levels.
-
B.
Indian Muslim politician
An Indian Muslim politician is a public officeholder or political leader in India who identifies as Muslim and participates in the country’s political processes, representing constituents’ interests within its democratic and often secular institutional framework.
-
C.
Nepalese politician
A Nepalese politician is a public figure from Nepal who engages in political activities, represents constituents, and participates in the governance and policymaking processes of the country.
-
D.
Indian National Congress politician
An Indian National Congress politician is a public officeholder or political figure in India who is affiliated with, represents, or works under the banner of the Indian National Congress party in legislative, executive, or organizational roles.
-
E.
Hazara politician
A Hazara politician is a public officeholder or political figure of Hazara ethnic origin who participates in governance, policy-making, and representation of Hazara community interests within a political system.
- F. None of above. chosen
Provenance (1 batch)
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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:14 a.m.