Triple
T2166369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Hospital for Mothers and Babies |
E46917
|
entity |
| Predicate | patientType |
P12412
|
FINISHED |
| Object | mothers |
—
|
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: mothers | Statement: [British Hospital for Mothers and Babies, patientType, mothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patientType Context triple: [British Hospital for Mothers and Babies, patientType, mothers]
-
A.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
B.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
C.
hasPatient
chosen
Indicates that an action, event, or process involves a specific entity as the one undergoing or receiving its effects (the patient).
-
D.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
E.
payerType
Indicates the type or category of entity responsible for making a payment in the relationship.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeab223881908aaa2bc4f85329cc |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.