Triple
T1212799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bermuda Police Service |
E26038
|
entity |
| Predicate | nonEmergencyNumber |
P5467
|
FINISHED |
| Object | 295-0011 |
—
|
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: 295-0011 | Statement: [Bermuda Police Service, nonEmergencyNumber, 295-0011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonEmergencyNumber Context triple: [Bermuda Police Service, nonEmergencyNumber, 295-0011]
-
A.
usesEmergencyNumber
Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
-
B.
associatedNumber
chosen
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
C.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
D.
officeNumber
Indicates the specific room or suite number assigned to an office within a building or complex.
-
E.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bde6cb608190b77fc5c47083e4b7 |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.