Triple
T9380479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Infirmary of Glasgow |
E225768
|
entity |
| Predicate | hasMajorRedevelopment |
P54016
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Royal Infirmary of Glasgow, hasMajorRedevelopment, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRedevelopment Context triple: [Royal Infirmary of Glasgow, hasMajorRedevelopment, 1980s]
-
A.
hasRedevelopmentProgram
Indicates that an entity is subject to or involved in a planned process of redevelopment, typically through an organized program or initiative.
-
B.
majorRedevelopmentPeriod
chosen
Indicates a time span during which a place or structure underwent significant redevelopment or large-scale renovation.
-
C.
hasMajorReconstruction
Indicates that an entity has undergone a significant or extensive reconstruction or renovation.
-
D.
hasRedevelopmentGoal
Indicates that an entity is associated with a specific objective or target related to redevelopment or renewal activities.
-
E.
redevelopmentInvolved
Indicates that an entity participated in or was associated with the process of redeveloping another entity, such as land, property, or infrastructure.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bc94108190a1b8146a78166009 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.