Triple
T29698411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Augusta |
E751415
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era stronghold |
C38605
|
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: colonial-era stronghold Context triple: [Fort Augusta, instanceOf, colonial-era stronghold]
-
A.
colonial stronghold
chosen
A colonial stronghold is a heavily fortified settlement or military outpost established by a colonizing power to secure control, protect resources, and project authority over a foreign territory.
-
B.
colonial-era trading outpost
A colonial-era trading outpost is a remote settlement established by an imperial power to facilitate the exchange of goods, resources, and information between the colonizing nation and local populations, often serving as a strategic hub for commerce, governance, and cultural contact.
-
C.
colonial-era monument
A colonial-era monument is a public structure or statue erected during or commemorating a period of colonial rule, symbolizing the power, values, and historical narratives of the colonizing authority.
-
D.
Spanish colonial fortification
A Spanish colonial fortification is a military structure built by the Spanish Empire in its overseas territories to defend strategic ports, settlements, and trade routes from rival powers and local resistance.
-
E.
fortified island stronghold
A fortified island stronghold is a heavily defended, self-contained military bastion built on an island, designed to control surrounding waters and withstand prolonged siege or assault.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:22 p.m.