Triple
T22333263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss Point, Mississippi |
E552076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipality in Mississippi |
C46122
|
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 Mississippi Context triple: [Moss Point, Mississippi, instanceOf, municipality in Mississippi]
-
A.
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.
-
B.
municipality in Arkansas
A municipality in Arkansas is an incorporated local government entity, such as a city or town, that operates under state law to provide public services and governance to its residents within defined geographic boundaries.
-
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.
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.
-
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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.