Triple
T6782929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tameside General Hospital |
E155727
|
entity |
| Predicate | emergencyServiceCoverage |
P59476
|
FINISHED |
| Object | 24-hour |
—
|
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: 24-hour | Statement: [Tameside General Hospital, emergencyServiceCoverage, 24-hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyServiceCoverage Context triple: [Tameside General Hospital, emergencyServiceCoverage, 24-hour]
-
A.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
B.
emergencyServicesRegion
Indicates the geographic region within which specific emergency services are responsible for responding to incidents.
-
C.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
-
D.
hasEmergencyCare
chosen
Indicates that an entity provides or is equipped with emergency medical care services for another entity or individuals.
-
E.
medicalCoverageAfter
Indicates that one entity’s medical insurance coverage begins or applies after the time, event, or coverage period associated with 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d289958481908ad4f9467a107083 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.