Triple
T31186709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruchill |
E795064
|
entity |
| Predicate | hasFormerSite |
P4380
|
FINISHED |
| Object | Ruchill Hospital |
—
|
NE NERFINISHED |
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: Ruchill Hospital | Statement: [Ruchill, hasFormerSite, Ruchill Hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerSite Context triple: [Ruchill, hasFormerSite, Ruchill Hospital]
-
A.
formerSiteOf
chosen
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
B.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
C.
hasFormerVenueType
Indicates that an entity previously had a specific type of venue, but that venue type is no longer current.
-
D.
hasFormerStation
Indicates that an entity previously had a particular station (e.g., a stop, depot, or facility) that is no longer in active use or part of its current infrastructure.
-
E.
formerSiteOwner
Indicates that one entity previously owned or controlled a particular site but no longer does so.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 29, 2026, 9:08 p.m.