Triple
T13717122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Mississippi Medical Center |
E328929
|
entity |
| Predicate | typeOfCareProvided |
P7500
|
FINISHED |
| Object | primary 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: primary care | Statement: [University of Mississippi Medical Center, typeOfCareProvided, primary care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCareProvided Context triple: [University of Mississippi Medical Center, typeOfCareProvided, primary care]
-
A.
providesCareSetting
Indicates that one entity serves as the care environment or setting in which another entity receives or delivers care.
-
B.
healthcareType
chosen
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
C.
natureOfService
Indicates the specific type or category of service being provided or performed in a given context.
-
D.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
E.
plannedServiceType
Indicates the category or kind of service that has been scheduled or planned to be provided.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd4398f0448190810c840a82228706 |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.