Triple
T1707036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuerzas Aeromóviles del Ejército de Tierra |
E36894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aviation unit |
C2497
|
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: military aviation unit Context triple: [Fuerzas Aeromóviles del Ejército de Tierra, instanceOf, military aviation unit]
-
A.
fighter squadron
A fighter squadron is a military aviation unit composed of multiple fighter aircraft and their personnel, organized to conduct air-to-air and air-to-ground combat missions under a unified command.
-
B.
aerial warfare service branch
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.
-
C.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
D.
special operations aviation regiment
A special operations aviation regiment is a military aviation unit specialized in providing highly trained air support, insertion, extraction, and logistical capabilities for special operations forces in complex and high-risk environments.
-
E.
military aerobatic team
A military aerobatic team is a specialized group of highly trained military pilots who perform precise, coordinated aerial maneuvers in formation to demonstrate flying skill, promote their service branch, and support public relations and recruitment efforts.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.