Triple
T34450155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortress El Fraile |
E884341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States coastal artillery 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: United States coastal artillery fort Context triple: [Fortress El Fraile, instanceOf, United States coastal artillery 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.
United States Coast Guard facility
A United States Coast Guard facility is a designated site, such as a station, base, or support installation, used to house personnel, equipment, and operations that support the Coast Guard’s maritime safety, security, law enforcement, and environmental protection missions.
-
C.
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.
-
D.
U.S. Navy training range
A U.S. Navy training range is a designated sea, air, or land area equipped and managed for conducting military exercises, weapons testing, and operational training to prepare naval forces for real-world missions.
-
E.
former naval base
A former naval base is a decommissioned military maritime facility that once supported naval operations but has since been repurposed, abandoned, or converted to civilian use.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.