Triple
T12618454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fayetteville, Arkansas |
E301315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Arkansas |
C32239
|
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 Arkansas Context triple: [Fayetteville, Arkansas, instanceOf, municipality in Arkansas]
-
A.
county in Arkansas
A county in Arkansas is an administrative and geographic subdivision of the state of Arkansas that serves as a local level of government, providing services such as law enforcement, courts, and public records for its residents.
-
B.
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.
-
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.
county in Mississippi
A county in Mississippi is a local governmental subdivision of the state that serves as an administrative and geographic unit for delivering public services, managing records, and organizing political representation.
-
E.
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.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:13 p.m.