Triple
T6961090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Union Trading Post National Historic Site |
E161369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reconstructed fur trading post |
C8110
|
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: reconstructed fur trading post Context triple: [Fort Union Trading Post National Historic Site, instanceOf, reconstructed fur trading post]
-
A.
fur trading post
A fur trading post is a remote commercial outpost where trappers, Indigenous peoples, and traders exchanged animal pelts for goods such as tools, weapons, textiles, and provisions.
-
B.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
-
C.
Sauk settlement
A Sauk settlement is a community or village established and inhabited by the Sauk (Sac) people, typically organized around kinship networks, seasonal subsistence activities, and cultural practices in their traditional homelands.
-
D.
reconstructed historic site
chosen
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
E.
former whaling station
A former whaling station is a decommissioned coastal facility once used for hunting, processing, and exporting whales, now typically abandoned, repurposed, or preserved as a historical site.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:29 p.m.