Triple
T4986733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FEMA Region III |
E112021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government agency regional office |
C1183
|
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: government agency regional office Context triple: [FEMA Region III, instanceOf, government agency regional office]
-
A.
territorial government agency
A territorial government agency is a public organization established by a territorial authority to administer laws, deliver services, and manage resources within a defined geographic area.
-
B.
independent regional agency
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
C.
government agency division
A government agency division is a specialized organizational unit within a larger government agency that focuses on a specific set of functions, programs, or policy areas to support the agency’s overall mission.
-
D.
regional administrative branch
chosen
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
state government agency
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.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:34 p.m.