Triple
T25929490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabre Army Heliport |
E653395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Army helicopter facility |
C50101
|
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: U.S. Army helicopter facility Context triple: [Sabre Army Heliport, instanceOf, U.S. Army helicopter facility]
-
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.
U.S. Army aviation program
The U.S. Army aviation program encompasses the development, training, operation, and maintenance of rotary- and fixed-wing aircraft to provide air mobility, reconnaissance, attack, and support capabilities for Army missions.
-
C.
army aviation unit
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
D.
U.S. Army aviation battalion
A U.S. Army aviation battalion is a military unit that organizes, operates, and sustains multiple helicopter or fixed-wing aircraft companies to provide air assault, reconnaissance, transport, medical evacuation, and support capabilities to ground forces.
-
E.
U.S. Army aviation brigade
A U.S. Army aviation brigade is a large, modular combat unit that provides coordinated helicopter and unmanned aircraft support for assault, reconnaissance, transport, and logistical missions in support of ground forces.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:36 a.m.