Triple
T6151794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow United States Senator for the District of Columbia |
E137220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-voting representative position |
C509
|
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: non-voting representative position Context triple: [Shadow United States Senator for the District of Columbia, instanceOf, non-voting representative position]
-
A.
nonpartisan legislative office
A nonpartisan legislative office is an organizational unit within a legislative body that provides neutral, fact-based research, analysis, and administrative support to all members regardless of political affiliation.
-
B.
parliamentary position
chosen
A parliamentary position is a formal role or office held by an individual within a legislative body, encompassing specific duties, powers, and responsibilities in the conduct of parliamentary business.
-
C.
Cabinet position
A cabinet position is a high-level government role, typically heading an executive department, appointed to advise and assist the chief executive in implementing public policy.
-
D.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
-
E.
organizational representative
An organizational representative is an individual or entity authorized to act on behalf of an organization in communications, decisions, and formal transactions.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:16 p.m.