Triple
T936095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isle of Man Constabulary |
E20196
|
entity |
| Predicate | usesEmergencyNumber |
P21774
|
FINISHED |
| Object | 999 |
—
|
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: 999 | Statement: [Isle of Man Constabulary, usesEmergencyNumber, 999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEmergencyNumber Context triple: [Isle of Man Constabulary, usesEmergencyNumber, 999]
-
A.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
B.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
C.
hasEmergencyIntercoms
Indicates that an entity is equipped with emergency intercom devices available for use in urgent or crisis situations.
-
D.
emergencyPower
Indicates that an entity has backup or auxiliary power available or activated for use during emergencies or primary power failures.
-
E.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b36558588190a2a9c710073624d1 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.