Triple
T6766728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frimley Park Hospital |
E154737
|
entity |
| Predicate | hasMaternityUnit |
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: [Frimley Park Hospital, hasMaternityUnit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaternityUnit Context triple: [Frimley Park Hospital, hasMaternityUnit, yes]
-
A.
hasClinicalUnit
Indicates that an entity is associated with or belongs to a specific clinical unit or department within a healthcare setting.
-
B.
hasNurse
Indicates that an entity is assigned or associated with a nurse who provides care or medical support to it.
-
C.
hasHospitalType
Indicates that a hospital is classified as belonging to a specific type or category (e.g., general, specialized, teaching).
-
D.
containsHospital
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
-
E.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
- F. None of above. chosen
Provenance (4 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2303c6881909405f0d6089dbe12 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:12 p.m.