Triple
T36985357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 112 Pct |
E914945
|
entity |
| Predicate | hasLawEnforcementLevel |
P183058
|
FINISHED |
| Object | local |
—
|
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: local | Statement: [112 Pct, hasLawEnforcementLevel, local]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLawEnforcementLevel Context triple: [112 Pct, hasLawEnforcementLevel, local]
-
A.
lawEnforcementLevel
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
-
B.
lawEnforcementAgencyLevel
chosen
Indicates the jurisdictional or administrative level at which a law enforcement agency operates (e.g., local, regional, national).
-
C.
lawEnforcementStatus
Indicates the relationship between an entity and its current standing or condition with respect to law enforcement, such as being under investigation, wanted, detained, or cleared.
-
D.
isPartOfLawEnforcementSystem
Indicates that an entity belongs to, operates within, or functionally contributes to a law enforcement system or framework.
-
E.
isLawEnforcement
Indicates that an entity serves in an official capacity to enforce laws, maintain public order, and uphold legal regulations.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:14 p.m.