Triple
T28387069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bong Air Force Base (former) in Wisconsin |
E719046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | planned United States Air Force base |
C1085
|
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: planned United States Air Force base Context triple: [Bong Air Force Base (former) in Wisconsin, instanceOf, planned United States Air Force base]
-
A.
United States Air Force base
chosen
A United States Air Force base is a military installation that supports Air Force operations through facilities for aircraft, personnel, training, logistics, and command and control activities.
-
B.
former air force base
A former air force base is a decommissioned military airfield and associated facilities that once supported air force operations but has since been closed, repurposed, or abandoned.
-
C.
United States Air Force training range
A United States Air Force training range is a designated area of land, airspace, or water used to conduct realistic military training, testing, and evaluation of aircraft, weapons, and tactics under controlled conditions.
-
D.
air reserve base
An air reserve base is a military installation that supports, trains, and deploys reserve air forces, providing facilities, equipment, and infrastructure for part-time and mobilizable air personnel.
-
E.
military base agreement
A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:10 a.m.