Triple
T32270383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TTC special constables (patrol) |
E824400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement support role |
C31640
|
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: law enforcement support role Context triple: [TTC special constables (patrol), instanceOf, law enforcement support role]
-
A.
law enforcement role
chosen
A law enforcement role is a position within an authorized agency responsible for upholding laws, maintaining public order, preventing and investigating crime, and protecting the safety and rights of individuals and communities.
-
B.
policing support entity
A policing support entity is an organization or unit that assists law enforcement agencies by providing specialized services, resources, or expertise to enhance public safety and policing effectiveness.
-
C.
law enforcement resource
A law enforcement resource is any personnel, equipment, technology, information, or funding allocated to support the prevention, investigation, and enforcement of laws and public safety.
-
D.
law enforcement tool
A law enforcement tool is any device, technology, or system used by authorities to prevent, detect, investigate, or respond to criminal activity while supporting public safety and legal compliance.
-
E.
civilian policing role
A civilian policing role is a non-sworn position within a law enforcement or public safety agency that supports policing functions—such as administration, analysis, community outreach, or technical services—without exercising arrest powers or carrying firearms.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.