Triple
T24582650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital Universitario La Paz |
E608293
|
entity |
| Predicate | hasPediatricServices |
P77388
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hospital Universitario La Paz, hasPediatricServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPediatricServices Context triple: [Hospital Universitario La Paz, hasPediatricServices, yes]
-
A.
hasPediatricHospital
Indicates that an entity possesses or is associated with a hospital facility that provides medical services specifically for children.
-
B.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
-
C.
hasPediatricUse
Indicates that something is intended, approved, or suitable for use in children or pediatric contexts.
-
D.
hasChildCare
Indicates that an entity provides, offers, or is associated with child care services or facilities for children.
-
E.
hasClinicalService
chosen
Indicates that an entity provides, offers, or is associated with a specific clinical service.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a983a4408190acdf29ccd52be9d4 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.