Triple
T838895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Aerospace Defense Command |
E18132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air and space defense command |
C2925
|
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: air and space defense command Context triple: [North American Aerospace Defense Command, instanceOf, air and space defense command]
-
A.
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.
-
B.
reserve component of the United States Air Force
The reserve component of the United States Air Force is the part-time military force composed of Air Force Reserve and Air National Guard units that support and augment the active-duty Air Force during peacetime and wartime operations.
-
C.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
D.
naval air service
A naval air service is a military aviation branch responsible for operating aircraft and related support units in direct support of a nation's navy, including maritime patrol, fleet air defense, anti-submarine warfare, and carrier-based operations.
-
E.
aerial warfare service branch
chosen
An aerial warfare service branch is a military organization responsible for conducting and supporting combat and operational activities in the air and, increasingly, in space and cyberspace domains.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.