Triple
T2012222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelvingrove Art Gallery and Museum |
E43712
|
entity |
| Predicate | reopenedAfterRefurbishment |
P5418
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Kelvingrove Art Gallery and Museum, reopenedAfterRefurbishment, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterRefurbishment Context triple: [Kelvingrove Art Gallery and Museum, reopenedAfterRefurbishment, 2006]
-
A.
reopenedAfterRedevelopment
chosen
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
B.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
C.
renovatedFrom
Indicates that one entity has been updated, improved, or restored by modifying or reworking an earlier version represented by another entity.
-
D.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
E.
reopenedInNewBuilding
Indicates that an entity, after being closed or relocated, has resumed operations in a different, newly constructed building.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.