Triple
T17358791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Columbia at-large congressional district |
E422014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-voting congressional district |
C1141
|
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 congressional district Context triple: [District of Columbia at-large congressional district, instanceOf, non-voting congressional district]
-
A.
United States congressional district
A United States congressional district is a geographically defined area within a state that elects one member to the U.S. House of Representatives.
-
B.
non-voting member of the United States House of Representatives
A non-voting member of the United States House of Representatives is a delegate or resident commissioner who represents a U.S. territory or district, participates in debates and committees, but generally lacks the right to vote on final passage of legislation on the House floor.
-
C.
electoral district
chosen
An electoral district is a geographically defined area represented by an elected official, within which eligible voters choose their representatives in a legislative body.
-
D.
congressional district system
A congressional district system is a method of dividing a country or state into geographically defined electoral areas, each of which elects its own representative to a legislative body.
-
E.
Virginia congressional district
A Virginia congressional district is a geographically defined area within the Commonwealth of Virginia from which voters elect a single representative to the United States House of Representatives.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.