Triple
T3622781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakwood Park, Missouri |
E76764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Missouri |
C13510
|
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 Missouri Context triple: [Oakwood Park, Missouri, instanceOf, municipality in Missouri]
-
A.
county in Missouri
A county in Missouri is an administrative subdivision of the state that provides local government services, maintains public records, and oversees regional functions such as law enforcement, courts, and infrastructure for the communities within its boundaries.
-
B.
county of Missouri
A county of Missouri is a local governmental subdivision of the state of Missouri that provides regional administration, services, and governance for the residents within its defined geographic boundaries.
-
C.
county of Kansas
A county of Kansas 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 and 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.
county of Minnesota
A county of Minnesota is an administrative and geographic subdivision of the U.S. state of Minnesota that provides local government services, governance, and regional organization for its residents and communities.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:23 p.m.