Triple
T8774159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort St. Anthony |
E208535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European-built coastal fort |
C3795
|
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: European-built coastal fort Context triple: [Fort St. Anthony, instanceOf, European-built coastal fort]
-
A.
historic coastal fort
chosen
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.
fortified town
A fortified town is a settlement enclosed by defensive structures such as walls, towers, and gates, designed to protect its inhabitants and resources from external threats.
-
C.
fortified settlement
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
D.
sea fort
A sea fort is a fortified structure built on or near the sea, typically on artificial islands, rocks, or coastal waters, designed to defend harbors, coastlines, or strategic maritime routes.
-
E.
fortified building
A fortified building is a heavily constructed structure designed with defensive features such as thick walls, limited entry points, and protective battlements to resist attacks and provide security for its occupants.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:41 p.m.