Triple
T27622768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral Complaints Commission |
E696120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Afghan public body |
C22998
|
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: Afghan public body Context triple: [Electoral Complaints Commission, instanceOf, Afghan public body]
-
A.
Afghan political organization
chosen
An Afghan political organization is a structured group operating within Afghanistan’s political sphere that seeks to influence governance, policy, and public opinion through formal or informal means.
-
B.
Afghan national
An Afghan national is an individual who holds legal citizenship of Afghanistan, typically through birth, descent, or naturalization, and is recognized as such by the Afghan state.
-
C.
Pakistani organization
A Pakistani organization is a formally structured group or institution operating within or closely associated with Pakistan, established to pursue specific social, economic, political, cultural, or religious objectives under relevant national laws and norms.
-
D.
Omani government body
An Omani government body is an official public-sector organization in the Sultanate of Oman responsible for implementing national policies, delivering public services, and regulating specific domains in accordance with Omani law and state objectives.
-
E.
Indonesian government body
An Indonesian government body is an official public institution established by the state to formulate, implement, and oversee policies, regulations, and services within a specific area of governance in Indonesia.
- F. None of above.
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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:15 p.m.