Triple
T7027041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Auburn Hospital |
E162973
|
entity |
| Predicate | hasMaternityServices |
P73148
|
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: [Mount Auburn Hospital, hasMaternityServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternityServices Context triple: [Mount Auburn Hospital, hasMaternityServices, yes]
-
A.
hasMaternityUnit
chosen
Indicates that a facility or organization includes or operates a maternity unit where childbirth and related maternal care services are provided.
-
B.
hasNurse
Indicates that an entity is assigned or associated with a nurse who provides care or medical support to it.
-
C.
hasMunicipalService
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasHealthcareInfrastructure
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.