Triple
T5257608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force Thunderbirds |
E118739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aerobatics team |
C2496
|
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 aerobatics team Context triple: [United States Air Force Thunderbirds, instanceOf, military aerobatics team]
-
A.
military aerobatic team
chosen
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.
-
B.
aerobatic display team
An aerobatic display team is a group of highly trained pilots who perform coordinated, precision flying maneuvers in formation to entertain audiences and demonstrate aircraft capabilities.
-
C.
multinational airborne army formation
A multinational airborne army formation is a coordinated military unit composed of airborne-capable forces from multiple nations, trained and organized to conduct joint air-delivered operations under a unified command structure.
-
D.
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.
-
E.
air force formation
An air force formation is an organized arrangement of multiple military aircraft flying together in a coordinated pattern to achieve tactical, strategic, or ceremonial objectives.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:50 p.m.