Triple
T31528454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daisy Hill Hospital |
E804406
|
entity |
| Predicate | provides24HourEmergencyCare |
P192147
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Daisy Hill Hospital, provides24HourEmergencyCare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provides24HourEmergencyCare Context triple: [Daisy Hill Hospital, provides24HourEmergencyCare, true]
-
A.
hasEmergencyCare
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
-
B.
offers24HourCare
chosen
Indicates that an entity provides continuous, around-the-clock care or service 24 hours a day.
-
C.
providesCareDuring
Indicates that one entity delivers care, assistance, or support to another entity throughout a specific period or event.
-
D.
hasEmergencyServiceProvider
Indicates that an entity is associated with or served by a specific emergency service provider (such as police, fire, or medical services).
-
E.
providesComprehensiveCare
Indicates that one entity delivers thorough, wide-ranging support or services addressing multiple needs of another entity.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 30, 2026, 10 p.m.