Triple
T6957237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament Street (Hamilton, Bermuda) |
E161275
|
entity |
| Predicate | hasEmergencyServicesAccess |
P66099
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Parliament Street (Hamilton, Bermuda), hasEmergencyServicesAccess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyServicesAccess Context triple: [Parliament Street (Hamilton, Bermuda), hasEmergencyServicesAccess, yes]
-
A.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
B.
hasEmergencyCare
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
-
C.
hasEmergencyTransport
Indicates that an entity provides, is equipped with, or has access to emergency transportation services or vehicles.
-
D.
hasEmergencyLevel
Indicates that an entity is associated with a specific degree or severity of emergency status.
-
E.
hasAmenityAccessTo
chosen
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dad0e52081908b524dc6a66bab01 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.