Triple
T17669892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiser, Idaho |
E440491
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Idaho |
C39513
|
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: municipality in Idaho Context triple: [Weiser, Idaho, instanceOf, municipality in Idaho]
-
A.
county in Idaho
A county in Idaho is an administrative subdivision of the state of Idaho that has its own local government and defined geographic boundaries, responsible for providing regional services such as law enforcement, courts, and infrastructure management.
-
B.
municipality in Colorado
A municipality in Colorado is an incorporated local government entity—such as a city or town—established under state law to provide public services, governance, and regulations within a defined geographic area in Colorado.
-
C.
municipality in Indiana
A municipality in Indiana is a legally incorporated local government entity, such as a city or town, within the state of Indiana that provides public services and governance to its residents under state law.
-
D.
municipality in Missouri
A municipality in Missouri is an incorporated local government entity within the state of Missouri, such as a city, town, or village, that has legal authority to provide services and enact ordinances for its residents.
-
E.
municipality in Pennsylvania
A municipality in Pennsylvania is a legally defined local government entity—such as a city, borough, township, or town—responsible for providing public services and governance within its geographic boundaries in the state of Pennsylvania.
- F. None of above. chosen
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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 9:59 a.m.