Triple
T608297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Children’s Hospital |
E12041
|
entity |
| Predicate | emergencyServices |
P464
|
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: [Boston Children’s Hospital, emergencyServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyServices Context triple: [Boston Children’s Hospital, emergencyServices, yes]
-
A.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
B.
hasEmergencyServices
chosen
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
C.
emergencyPower
Indicates that an entity has backup or auxiliary power available or activated for use during emergencies or primary power failures.
-
D.
officersCalled
Indicates that law enforcement officers were summoned or notified to respond to a situation or incident.
-
E.
emergencyPowerRole
Indicates that an entity holds a role or responsibility specifically related to emergency power functions or authority.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df54eec8190af3f5f04c01d5d2a |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.