Triple
T7627541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 1 Photographic Reconnaissance Unit RAF |
E172673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | photographic reconnaissance unit |
C22619
|
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: photographic reconnaissance unit Context triple: [No. 1 Photographic Reconnaissance Unit RAF, instanceOf, photographic reconnaissance unit]
-
A.
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.
-
B.
aviation regiment
An aviation regiment is a military unit composed of multiple aircraft squadrons or flights, along with their supporting personnel and equipment, organized to conduct coordinated air operations.
-
C.
paratrooper unit
A paratrooper unit is a specialized military formation trained and equipped to deploy from aircraft by parachute to conduct airborne assaults, rapid insertions, and operations behind enemy lines.
-
D.
Polish Air Force unit
A Polish Air Force unit is an organizational entity within Poland’s air arm responsible for operating, maintaining, and supporting assigned aircraft and air defense systems to fulfill national defense and allied mission objectives.
-
E.
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.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:56 p.m.