Triple
T12228662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hong Kong Police Force |
E291417
|
entity |
| Predicate | policeNumberingSystem |
P103905
|
FINISHED |
| Object | UI number |
—
|
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: UI number | Statement: [Hong Kong Police Force, policeNumberingSystem, UI number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeNumberingSystem Context triple: [Hong Kong Police Force, policeNumberingSystem, UI number]
-
A.
policeNumber
Indicates that an entity is associated with a specific police-related identification or reference number.
-
B.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
C.
policePackageCode
Indicates that an entity is associated with a specific police package code, typically identifying a law-enforcement-related configuration, option, or classification.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
routeNumberingAuthority
Indicates the authority or organization responsible for assigning and managing the official number designation of a route.
- F. None of above. chosen
Provenance (4 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d92468052c819090546f36d009a64f |
completed | April 10, 2026, 4:25 p.m. |
Created at: April 8, 2026, 9:51 p.m.