Triple
T35088212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Mayo Composite project |
E1012637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British aviation project |
C16232
|
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: British aviation project Context triple: [Short Mayo Composite project, instanceOf, British aviation project]
-
A.
British military aircraft prototype
A British military aircraft prototype is an experimental or pre-production aircraft developed in the United Kingdom to test and refine new designs, technologies, or capabilities for potential adoption by the armed forces.
-
B.
military aircraft project
A military aircraft project is an organized effort to design, develop, test, and produce an aircraft intended for defense or combat roles, encompassing technical, logistical, financial, and strategic considerations.
-
C.
British Air Ministry specification
A British Air Ministry specification was an official document issued by the Air Ministry that defined the performance, design, and operational requirements for new military aircraft or equipment to be developed for the Royal Air Force.
-
D.
Royal Air Force aircraft variant
A Royal Air Force aircraft variant is a specific version of an aircraft type that has been modified or configured to meet particular operational, technical, or role-based requirements of the RAF.
-
E.
unbuilt aircraft project
chosen
An unbuilt aircraft project is a conceptual or proposed airplane design that was planned and possibly studied or partially developed but never constructed or flown.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.