Triple
T27270239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascension St. Vincent |
E688028
|
entity |
| Predicate | careContinuum |
P162297
|
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: [Ascension St. Vincent, careContinuum, primary care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careContinuum Context triple: [Ascension St. Vincent, careContinuum, primary care]
-
A.
careContinuum
chosen
Indicates a relationship in which care or services are provided in a coordinated, continuous manner across different stages, settings, or levels of support.
-
B.
careApproach
Indicates the method, strategy, or manner in which care or support is provided to someone or something.
-
C.
primaryContinuityOf
Indicates that one entity serves as the main or principal continuation or extension of another entity in a sequence or process.
-
D.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
-
E.
care
Indicates showing concern, attention, or responsibility for the well-being or 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 10:58 a.m.