Triple
T30071119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | new-build P2 No. 2007 Prince of Wales |
E764184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heritage engineering project |
C28696
|
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: heritage engineering project Context triple: [new-build P2 No. 2007 Prince of Wales, instanceOf, heritage engineering project]
-
A.
heritage conservation programme
A heritage conservation programme is an organized set of policies, actions, and resources aimed at identifying, protecting, and sustainably managing cultural and natural heritage for present and future generations.
-
B.
civil engineering landmark
A civil engineering landmark is a significant structure or project—such as a bridge, dam, tunnel, or roadway—that exemplifies notable achievement, innovation, or historical importance in the field of civil engineering.
-
C.
heritage asset
chosen
A heritage asset is a building, monument, site, landscape, or object of historical, cultural, architectural, or archaeological significance that is preserved for its value to present and future generations.
-
D.
era of hydraulic engineering
The era of hydraulic engineering is a historical period characterized by the systematic design, construction, and management of water control structures and systems to support human activities such as agriculture, urbanization, transportation, and energy production.
-
E.
heritage irrigation system
A heritage irrigation system is a historically significant network of water management structures and practices preserved for their cultural, technological, and agricultural value.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7 p.m.