Triple
T8777824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Mississippi Regional Medical Center |
E208639
|
entity |
| Predicate | emergencyServiceLevel |
P33503
|
FINISHED |
| Object | 24-hour emergency care |
—
|
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 emergency care | Statement: [Southwest Mississippi Regional Medical Center, emergencyServiceLevel, 24-hour emergency care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyServiceLevel Context triple: [Southwest Mississippi Regional Medical Center, emergencyServiceLevel, 24-hour emergency care]
-
A.
emergencyService
Indicates that one entity provides or is associated with urgent, time-critical assistance or response to another entity in emergency situations.
-
B.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
C.
emergencyRole
Indicates that an entity holds a specific function, responsibility, or authority in emergency or crisis situations.
-
D.
hasEmergencyLevel
Indicates that an entity is associated with a specific degree or severity of emergency status.
-
E.
typeOfEmergencyService
chosen
Indicates the specific category or kind of emergency service associated with or provided in a given situation.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f51b3d48190b542a0423d3938e0 |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.