Triple
T16963242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana law enforcement agencies |
E411480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public safety organization grouping |
C6030
|
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: public safety organization grouping Context triple: [Indiana law enforcement agencies, instanceOf, public safety organization grouping]
-
A.
public safety agency
A public safety agency is an organization responsible for protecting the public from threats and hazards by preventing, responding to, and managing emergencies, crimes, and disasters within a community or jurisdiction.
-
B.
legal organization collective
A legal organization collective is a formally recognized group of individuals or entities that operates under a shared legal structure to pursue common organizational goals, rights, and responsibilities.
-
C.
umbrella organisation
chosen
An umbrella organisation is a central body that unites, coordinates, and represents multiple related groups or entities under a common structure or purpose.
-
D.
civilian auxiliary organization
A civilian auxiliary organization is a volunteer-based group of non-military citizens that supports and augments the capabilities, missions, or services of a governmental or official institution, often in areas like emergency response, public safety, or community outreach.
-
E.
beach safety organization
A beach safety organization is a group dedicated to preventing accidents and promoting safe behavior at beaches through education, monitoring conditions, and coordinating rescue and emergency response services.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:31 a.m.