Triple
T22362060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDOT |
E552801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mississippi state agency |
C2542
|
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: Mississippi state agency Context triple: [MDOT, instanceOf, Mississippi state agency]
-
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.
state government agency
chosen
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
C.
New York State government agency component
A New York State government agency component is an organizational unit within a state agency, such as a division, bureau, or office, that performs specific statutory or administrative functions on behalf of the agency.
-
D.
former district of Louisiana Territory
A former district of Louisiana Territory is an obsolete administrative subdivision that once functioned as a regional governing unit within the historical U.S. Louisiana Territory before being reorganized into new territorial or state jurisdictions.
-
E.
former county of Missouri
A former county of Missouri is an administrative division that once existed as a distinct county within the state but has since been dissolved, renamed, merged, or otherwise reorganized so that it no longer functions as an independent county government.
- F. None of above.
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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.