Triple
T23593913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 148 Squadron RAF |
E582560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special duties squadron |
C47847
|
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: special duties squadron Context triple: [No. 148 Squadron RAF, instanceOf, special duties squadron]
-
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.
special operations aviation command
A special operations aviation command is a military organization that provides specialized, often clandestine air support—such as infiltration, exfiltration, resupply, and close air support—for special operations forces in high-risk or sensitive missions.
-
C.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
-
D.
force support squadron
A force support squadron is a military unit responsible for providing personnel, morale, welfare, and support services that sustain and enhance the readiness of operational forces.
-
E.
Special Purpose Marine Air-Ground Task Force
A Special Purpose Marine Air-Ground Task Force is a scalable, rapidly deployable, task-organized Marine Corps force combining ground, aviation, and logistics elements tailored to accomplish specific missions.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:42 p.m.