Triple
T7149378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin, Indiana |
E166652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Indiana |
C21453
|
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 Indiana Context triple: [Franklin, Indiana, instanceOf, municipality in Indiana]
-
A.
county of Indiana
A county of Indiana is a primary administrative and political subdivision of the U.S. state of Indiana, responsible for local governance, public services, and regional jurisdiction within its defined geographic boundaries.
-
B.
county in Indiana
A county in Indiana is an administrative subdivision of the state that serves as a local level of government, providing regional services, governance, and jurisdiction over a defined geographic area within Indiana.
-
C.
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.
-
D.
township in Illinois
A township in Illinois is a local governmental subdivision of a county that provides services such as road maintenance, property assessment, and general assistance to residents within its defined geographic boundaries.
-
E.
municipality in Virginia
A municipality in Virginia is a legally incorporated local government entity, such as a city or town, within the Commonwealth of Virginia that provides public services and exercises governmental authority over a defined geographic area.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.