Triple
T26887255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maternal Newborn Program |
E677075
|
entity |
| Predicate | providesCareDuring |
P176281
|
FINISHED |
| Object | pregnancy |
—
|
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: pregnancy | Statement: [Maternal Newborn Program, providesCareDuring, pregnancy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesCareDuring Context triple: [Maternal Newborn Program, providesCareDuring, pregnancy]
-
A.
providesComprehensiveCare
Indicates that one entity delivers thorough, wide-ranging support or services addressing multiple needs of another entity.
-
B.
providesCareSetting
Indicates that one entity serves as the care environment or setting in which another entity receives or delivers care.
-
C.
tookCareOf
Indicates that one entity provided care, support, or maintenance for another entity over a period of time.
-
D.
providesCareRegardlessOfAbilityToPay
Indicates that one party delivers care or services to another without considering or being limited by the recipient’s ability to pay.
-
E.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
- F. None of above. chosen
Provenance (4 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 5:42 a.m.