Triple
T38153240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Bartholomew the Less |
E952811
|
entity |
| Predicate | locatedInHospitalGrounds |
P50261
|
FINISHED |
| Object | St Bartholomew's Hospital |
E356290
|
NE 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: St Bartholomew's Hospital | Statement: [St Bartholomew the Less, locatedInHospitalGrounds, St Bartholomew's Hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHospitalGrounds Context triple: [St Bartholomew the Less, locatedInHospitalGrounds, St Bartholomew's Hospital]
-
A.
hospitalizedIn
Indicates that a person or patient is admitted for medical care and staying as an inpatient in a specified hospital or healthcare facility.
-
B.
containsHospital
chosen
Indicates that one entity includes or encompasses a hospital within its boundaries or composition.
-
C.
basedInHospitalSystem
Indicates that an entity operates within, is affiliated with, or is organizationally part of a particular hospital system.
-
D.
isWithinFacility
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
-
E.
hospitalLocation
Indicates the geographic place or address where a hospital is situated.
- F. None of above.
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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a418537f2a88190a250f30443563616 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.