Triple
T14828023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Area Commands (LACs) |
E348625
|
entity |
| Predicate | usesPolicingModel |
P21773
|
FINISHED |
| Object | community policing |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: community policing | Statement: [Local Area Commands (LACs), usesPolicingModel, community policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPolicingModel Context triple: [Local Area Commands (LACs), usesPolicingModel, community policing]
-
A.
policingModel
chosen
Indicates the approach, strategy, or framework used to organize and conduct policing activities or law enforcement operations.
-
B.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
C.
usedByLawEnforcementModel
Indicates that something is employed or utilized by law enforcement agencies or personnel, typically as a tool, method, or model in their operations or decision-making.
-
D.
enforcementModel
Indicates the method or framework by which rules, policies, or constraints are applied, monitored, and enforced within a system or interaction.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- F. None of above.
Provenance (3 batches)
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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.