Triple
T10877479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 813 Naval Air Squadron |
E256836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fleet Air Arm squadron |
C28932
|
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: Fleet Air Arm squadron Context triple: [813 Naval Air Squadron, instanceOf, Fleet Air Arm squadron]
-
A.
Royal Air Force squadron
A Royal Air Force squadron is a military aviation unit comprising aircraft, aircrew, and support personnel organized under a specific command structure to perform designated operational, training, or support roles.
-
B.
Royal Air Force Regiment squadron
A Royal Air Force Regiment squadron is a specialized ground combat and force protection unit of the RAF responsible for defending airfields, aircraft, and related assets through infantry, air defense, and security operations.
-
C.
Marine Aircraft Group
A Marine Aircraft Group is a U.S. Marine Corps aviation unit that commands, coordinates, and supports multiple squadrons and aviation support elements to provide air power for Marine Air-Ground Task Forces.
-
D.
Marine Aircraft Wing
A Marine Aircraft Wing is a major aviation command within the United States Marine Corps that provides combat-ready aircraft, aircrew, and support units to conduct air operations in support of Marine Air-Ground Task Forces.
-
E.
Royal Australian Air Force wing
A Royal Australian Air Force wing is a major operational or support formation comprising multiple squadrons and units, responsible for coordinating and delivering specific air power capabilities within the RAAF.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.