Triple
T14524292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | පෙදෙසේන කොටුව |
E340731
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese colonial fort |
C28905
|
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: Portuguese colonial fort Context triple: [පෙදෙසේන කොටුව, instanceOf, Portuguese colonial fort]
-
A.
Portuguese colonial building
chosen
A Portuguese colonial building is an architectural structure characterized by Iberian design elements—such as whitewashed walls, decorative tiles (azulejos), arched openings, and verandas—adapted to local climates and materials in former Portuguese territories.
-
B.
Portuguese trading post
A Portuguese trading post is a fortified coastal or riverside settlement established by Portugal during the Age of Exploration to control trade routes, facilitate commerce, and project imperial influence.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.