Triple
T34508287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KY-01 |
E885947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | congressional district of Kentucky |
C3702
|
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: congressional district of Kentucky Context triple: [KY-01, instanceOf, congressional district of Kentucky]
-
A.
Kentucky House of Representatives district
A Kentucky House of Representatives district is a geographically defined electoral area within the state of Kentucky from which one representative is elected to serve in the Kentucky House of Representatives.
-
B.
United States congressional district
chosen
A United States congressional district is a geographically defined area within a state that elects one member to the U.S. House of Representatives.
-
C.
county of Kentucky
A county of Kentucky is a local governmental and geographic subdivision of the Commonwealth of Kentucky, responsible for regional administration, services, and jurisdiction within its defined boundaries.
-
D.
Missouri House of Representatives district
A Missouri House of Representatives district is a geographically defined electoral area within the state of Missouri from which one representative is elected to serve in the Missouri House of Representatives.
-
E.
Tennessee House of Representatives district
A Tennessee House of Representatives district is a geographically defined electoral area within the state of Tennessee from which one representative is elected to serve in the Tennessee 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.