Triple
T31903439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdullah Ghaznavi |
E814483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public representative |
C35614
|
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: public representative Context triple: [Abdullah Ghaznavi, instanceOf, public representative]
-
A.
organizational representative
An organizational representative is an individual or entity authorized to act on behalf of an organization in communications, decisions, and formal transactions.
-
B.
representative peer
A representative peer is an individual within a group who is selected or recognized to act on behalf of others, conveying their perspectives, interests, and decisions in collective processes.
-
C.
government representative
chosen
A government representative is an individual elected or appointed to act on behalf of citizens or a constituency in the processes of governance, policy-making, and public administration.
-
D.
ceremonial representative
A ceremonial representative is an individual who symbolically embodies and publicly presents the authority, traditions, or identity of a group, organization, or state in formal events and rituals without necessarily holding executive power.
-
E.
plenipotentiary representative
A plenipotentiary representative is an individual, typically a diplomat, who is fully authorized to act on behalf of a state or organization in negotiations and decision-making.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, midnight