Triple
T30856110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oula |
E785923
|
entity |
| Predicate | careModelFeature |
P160817
|
FINISHED |
| Object | longer prenatal visits |
—
|
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: longer prenatal visits | Statement: [Oula, careModelFeature, longer prenatal visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careModelFeature Context triple: [Oula, careModelFeature, longer prenatal visits]
-
A.
careApproach
Indicates the method, strategy, or manner in which care or support is provided to someone or something.
-
B.
hasCareModel
Indicates that one entity uses, follows, or is governed by a particular model or approach to providing care.
-
C.
careContinuum
Indicates a relationship in which care or services are provided in a coordinated, continuous manner across different stages, settings, or levels of support.
-
D.
hasHealthCareCharacteristic
chosen
Indicates that an entity possesses a specific healthcare-related attribute, quality, or feature.
-
E.
welfareSupportFeature
Indicates that an entity provides, enables, or is associated with some form of welfare-related assistance or support.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691808b688190ba3f1f8e171117f7 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.