Triple
T29260695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restoration of Earlshall Castle, Fife |
E741836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic building restoration |
C5247
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic building restoration Context triple: [Restoration of Earlshall Castle, Fife, instanceOf, historic building restoration]
-
A.
historicBuilding
A historicBuilding is a structure of significant age recognized for its cultural, architectural, or historical importance and often preserved or protected for future generations.
-
B.
historic architecture
Historic architecture encompasses buildings and structures from past eras that embody the cultural, technological, and artistic values of the time in which they were created.
-
C.
historic preservation project
chosen
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
-
D.
cultural heritage restoration
Cultural heritage restoration is the process of preserving, repairing, and conserving artifacts, structures, and traditions to maintain their historical, cultural, and aesthetic significance for future generations.
-
E.
historic building record
A historic building record is a documented account that captures the architectural, cultural, and historical details of a building, including its design, construction, alterations, significance, and preservation status.
- F. None of above.
Provenance (1 batch)
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_69f0912065c08190bddd23e20e8ef18e |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:41 p.m.