Triple
T10743334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Macquarie Base Hospital |
E253381
|
entity |
| Predicate | emergencyCoverage |
P73303
|
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: [Port Macquarie Base Hospital, emergencyCoverage, 24-hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyCoverage Context triple: [Port Macquarie Base Hospital, emergencyCoverage, 24-hour]
-
A.
emergencyTypesCovered
Indicates that certain kinds of emergencies are included within the scope of coverage, protection, or response defined by the relationship.
-
B.
emergencyUse
Indicates that something is being used in response to an urgent or critical situation, typically as a temporary or exceptional measure.
-
C.
emergencyRole
Indicates that an entity holds a specific function, responsibility, or authority in emergency or crisis situations.
-
D.
emergencyService
chosen
Indicates that one entity provides or is associated with urgent, time-critical assistance or response to another entity in emergency situations.
-
E.
emergency
Indicates that an entity is in a state of urgent danger or critical need that requires immediate attention or action.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b5dd8c81908f1d9b126e4c3ae7 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.