Triple
T8727884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort St. John |
E207175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic military fortification |
C13905
|
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 fortification Context triple: [Fort St. John, instanceOf, historic military fortification]
-
A.
historic military fort
chosen
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 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.
-
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.
military fortification system
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.
-
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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.