Triple
T1038748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Henry |
E22422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic military fortress |
C876
|
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 fortress Context triple: [Fort Henry, instanceOf, historic military fortress]
-
A.
historic coastal fort
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 battlefield
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
C.
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.
-
D.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
-
E.
military fortification system
chosen
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.