Triple
T5271760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | police forces of St. Petersburg |
E119273
|
entity |
| Predicate | lawEnforcementArea |
P7908
|
FINISHED |
| Object | urban 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: urban policing | Statement: [police forces of St. Petersburg, lawEnforcementArea, urban policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawEnforcementArea Context triple: [police forces of St. Petersburg, lawEnforcementArea, urban policing]
-
A.
lawEnforcementLabel
Indicates that an entity has been designated, tagged, or classified by a law enforcement authority for monitoring, identification, or investigative purposes.
-
B.
lawEnforcementFunction
Indicates that an entity performs, is responsible for, or is associated with official law enforcement duties or activities.
-
C.
typeOfLawEnforcement
chosen
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
D.
lawEnforcementLevel
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
-
E.
enforcementAgency
Indicates that one entity serves as the authority responsible for enforcing laws, rules, or regulations related to another entity.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.