Triple
T7123337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Christiansborg |
E165998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former colonial fort |
C13905
|
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: former colonial fort Context triple: [Fort Christiansborg, instanceOf, former colonial fort]
-
A.
historic coastal fort
A historic coastal fort is a fortified structure built along a shoreline to defend strategic waterways and harbors from naval threats, often featuring thick masonry walls, artillery emplacements, and commanding views of the sea.
-
B.
former colonial settlement
A former colonial settlement is a community or territory originally established and governed by a foreign colonial power that has since transitioned to local or independent control, often retaining cultural, architectural, and institutional legacies of its colonial past.
-
C.
Dutch colonial building
A Dutch colonial building is a structure characterized by steeply pitched, often gambrel roofs, symmetrical facades, and practical, modest detailing reflecting Dutch architectural traditions adapted to colonial-era environments.
-
D.
historic military fort
chosen
A historic military fort is a fortified structure or complex built in the past for defense and military operations, often preserved today as a cultural and historical landmark.
-
E.
French colonial building
A French colonial building is a structure that blends traditional French architectural elements—such as ornate facades, balconies, and steep roofs—with local materials, climate adaptations, and regional design influences from former French colonies.
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:44 p.m.