Triple
T5764502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka Prefectural Police |
E127175
|
entity |
| Predicate | handlesEmergencyNumber |
P33775
|
FINISHED |
| Object | 110 |
—
|
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: 110 | Statement: [Fukuoka Prefectural Police, handlesEmergencyNumber, 110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesEmergencyNumber Context triple: [Fukuoka Prefectural Police, handlesEmergencyNumber, 110]
-
A.
usesEmergencyNumber
Indicates that an entity initiates contact or communication by dialing or otherwise employing an officially designated emergency telephone number.
-
B.
operatesEmergencyNumber
chosen
Indicates that an entity is responsible for running or managing an emergency telephone number service for another entity or region.
-
C.
emergencyPhoneNumber
Indicates that the object is a phone number designated for use in emergencies or urgent situations.
-
D.
operatesNonEmergencyNumber
Indicates that an entity is responsible for running or managing a telephone number designated for non-emergency inquiries or services.
-
E.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0296e12d48190bd120879723bb6e8 |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.