Triple
T29278991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort King, Florida |
E742319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century U.S. Army frontier outpost |
C11307
|
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: 19th-century U.S. Army frontier outpost Context triple: [Fort King, Florida, instanceOf, 19th-century U.S. Army frontier outpost]
-
A.
frontier-era building
A frontier-era building is a simple, utilitarian structure made from locally available materials, designed to provide basic shelter and function in remote, newly settled regions.
-
B.
frontier post
chosen
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.
Union Army fort
A Union Army fort is a fortified military installation constructed and used by United States forces during the Civil War to defend strategic locations, house troops, and support offensive and defensive operations.
-
D.
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.
-
E.
Union Army fortification
A Union Army fortification is a defensive military structure, such as an earthwork, fort, or entrenchment, constructed and used by United States forces during the Civil War to protect troops, control territory, and support offensive and defensive operations.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:53 p.m.