Triple
T26085591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NightingaleHospitals |
E657968
|
entity |
| Predicate | someSitesRepurposedAs |
P47023
|
FINISHED |
| Object | diagnostic hubs |
—
|
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: diagnostic hubs | Statement: [NightingaleHospitals, someSitesRepurposedAs, diagnostic hubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someSitesRepurposedAs Context triple: [NightingaleHospitals, someSitesRepurposedAs, diagnostic hubs]
-
A.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
-
C.
siteRedevelopedAs
Indicates that a site has been transformed, rebuilt, or repurposed into a new form, function, or development.
-
D.
rebuiltOnSiteOf
Indicates that a structure was reconstructed or newly built on the same physical location where an earlier structure once stood.
-
E.
reopenedOnSiteOf
Indicates that something has been reopened at the same physical location where it previously existed or operated.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6070013bc81908053ea20f7c7d71b |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:42 p.m.