Triple
T1585892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Monroe, Virginia |
E34064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic coastal fortification |
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 fortification Context triple: [Fort Monroe, Virginia, instanceOf, historic coastal fortification]
-
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 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.
-
C.
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.
-
D.
historic monument
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
E.
historic lighthouse
A historic lighthouse is a long-standing coastal beacon structure, often architecturally distinctive and culturally significant, originally built to guide maritime navigation and now frequently preserved as a heritage landmark.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:27 p.m.