Triple
T37687383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Hancock military installations |
E938407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic military installation complex |
C61674
|
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 military installation complex Context triple: [Fort Hancock military installations, instanceOf, historic military installation complex]
-
A.
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.
-
B.
historic watchtower complex
A historic watchtower complex is a group of strategically positioned, often interconnected towers and supporting structures originally built for surveillance, communication, and defense across a landscape.
-
C.
historic fortification structure
chosen
A historic fortification structure is a defensive building or complex, such as a castle, fortress, or city wall, constructed in the past to protect people, territory, or strategic locations from military threats.
-
D.
former military complex
A former military complex is a decommissioned installation once used for defense or armed forces operations, now repurposed, abandoned, or awaiting redevelopment.
-
E.
historic military storage buildings
Historic military storage buildings are purpose-built structures, often fortified and strategically located, designed to securely house weapons, ammunition, provisions, and other military supplies for past armed forces.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.