Triple
T38270927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fanling Police Station |
E1021204
|
entity |
| Predicate | policeRegion |
P59704
|
FINISHED |
| Object | New Territories |
—
|
NE NERFINISHED |
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: New Territories | Statement: [Fanling Police Station, policeRegion, New Territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeRegion Context triple: [Fanling Police Station, policeRegion, New Territories]
-
A.
policeAreaCode
Indicates that a police jurisdiction or authority is responsible for, or associated with, a specific area code or geographic region.
-
B.
policePrecinct
Indicates that a specified location, building, or area functions as or is designated as a police precinct.
-
C.
regionOfCrimes
Indicates the geographic area or jurisdiction in which the crimes occurred or are attributed to an entity.
-
D.
policeAreaPrecursorOf
Indicates that one police area served as a predecessor or earlier form of another police area in an administrative or organizational sequence.
-
E.
hasPoliceDistrict
chosen
Indicates that an entity falls under the jurisdiction or coverage area of a specific police district.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:30 p.m.