Triple
T37315077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instituto de Salud para el Bienestar |
E926310
|
entity |
| Predicate | tipo de atención |
P7500
|
FINISHED |
| Object | atención médica primaria |
—
|
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: atención médica primaria | Statement: [Instituto de Salud para el Bienestar, tipo de atención, atención médica primaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipo de atención Context triple: [Instituto de Salud para el Bienestar, tipo de atención, atención médica primaria]
-
A.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
B.
interventionType
Indicates the specific kind or category of action, treatment, or measure applied in an intervention.
-
C.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
D.
followUpType
Indicates the specific category or nature of a follow-up action or interaction that occurs after an initial event or communication.
-
E.
healthcareType
chosen
Indicates the category or kind of healthcare service, system, or coverage associated with an 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.