Triple
T23008443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Pacific Alaska Range Complex |
E572842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Air Force training range |
C47128
|
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: United States Air Force training range Context triple: [Joint Pacific Alaska Range Complex, instanceOf, United States Air Force training range]
-
A.
U.S. Navy training range
A U.S. Navy training range is a designated sea, air, or land area equipped and managed for conducting military exercises, weapons testing, and operational training to prepare naval forces for real-world missions.
-
B.
United States Air Force base
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.
-
C.
United States Marine Corps training area
A United States Marine Corps training area is a designated land, air, or sea space used to conduct realistic military exercises, weapons practice, and readiness training for Marine units.
-
D.
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.
-
E.
United States Air Force exercise
A United States Air Force exercise is a planned training event or series of operations designed to prepare Air Force personnel, units, and systems for real-world missions by simulating combat, support, or contingency scenarios.
- F. None of above. chosen
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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:51 p.m.