Triple
T7471894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Castle |
E176526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic coastal fortress |
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: historic coastal fortress Context triple: [Elizabeth Castle, instanceOf, historic coastal fortress]
-
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.
historic military fort
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.
-
C.
historic maritime signal tower
A historic maritime signal tower is a coastal structure once used to communicate navigational information, warnings, and messages to ships at sea through visual signals such as flags, lights, or semaphores.
-
D.
historic harbor
A historic harbor is a waterfront area that has played a significant role in maritime trade, travel, or defense over time and retains physical or cultural features reflecting its past.
-
E.
historic watchtower
A historic watchtower is a tall, fortified structure built in the past to provide elevated vantage points for surveillance, defense, and communication across surrounding lands or coastlines.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:41 p.m.