Triple
T1354136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Coastal Command |
E28948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | major command of the Royal Air Force |
C6954
|
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: major command of the Royal Air Force Context triple: [RAF Coastal Command, instanceOf, major command of the Royal Air Force]
-
A.
major command of the United States Air Force
A major command of the United States Air Force is a large, top-level organizational unit responsible for directing and overseeing a broad functional or geographic segment of the Air Force’s mission, resources, and operations.
-
B.
branch of the Royal Air Force
A branch of the Royal Air Force is a major organizational subdivision responsible for a specific functional area of air and space operations, support, or administration within the RAF.
-
C.
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.
-
D.
major command of the United States Army
A major command of the United States Army is a high-level organizational entity responsible for overseeing, directing, and supporting large-scale operational, administrative, or functional missions across multiple subordinate units and installations.
-
E.
Allied air force
Allied air force: The collective aerial military forces of nations united in a coalition, coordinating air operations to achieve shared strategic and tactical objectives in conflict.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.