Triple
T20739413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawker Tornado |
E509796
|
entity |
| Predicate | developedFromRequirement |
P39339
|
FINISHED |
| Object | Air Ministry Specification F.18/37 |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Air Ministry Specification F.18/37 | Statement: [Hawker Tornado, developedFromRequirement, Air Ministry Specification F.18/37]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Air Ministry Specification F.18/37 Context triple: [Hawker Tornado, developedFromRequirement, Air Ministry Specification F.18/37]
-
A.
Air Ministry Specification B.12/36
Air Ministry Specification B.12/36 was a British pre–Second World War requirement issued by the Air Ministry for the development of a new heavy bomber aircraft.
-
B.
Air Ministry Specification B.9/32
Air Ministry Specification B.9/32 was a British government requirement issued in the early 1930s for a new twin‑engined medium bomber, which led to the development of aircraft such as the Handley Page Hampden.
-
C.
Air Ministry Specification B.3/34
Air Ministry Specification B.3/34 was a British pre–Second World War Air Ministry requirement that called for the development of a new twin‑engine heavy night bomber, ultimately leading to the Armstrong Whitworth Whitley.
-
D.
Royal Aircraft Factory S.B.5
The Royal Aircraft Factory S.B.5 was an experimental British research aircraft built in the 1950s to investigate swept-wing and tailplane configurations that informed later high-speed fighter designs.
-
E.
Vickers Type 271 design studies
Vickers Type 271 design studies were early British aircraft design concepts by Vickers that formed the basis for the development of the Wellington Mk I bomber.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Air Ministry Specification F.18/37 Target entity description: Air Ministry Specification F.18/37 was a British pre–Second World War Air Ministry requirement calling for a new high-performance fighter aircraft design.
-
A.
Air Ministry Specification B.12/36
Air Ministry Specification B.12/36 was a British pre–Second World War requirement issued by the Air Ministry for the development of a new heavy bomber aircraft.
-
B.
Air Ministry Specification B.9/32
Air Ministry Specification B.9/32 was a British government requirement issued in the early 1930s for a new twin‑engined medium bomber, which led to the development of aircraft such as the Handley Page Hampden.
-
C.
Air Ministry Specification B.3/34
Air Ministry Specification B.3/34 was a British pre–Second World War Air Ministry requirement that called for the development of a new twin‑engine heavy night bomber, ultimately leading to the Armstrong Whitworth Whitley.
-
D.
Royal Aircraft Factory S.B.5
The Royal Aircraft Factory S.B.5 was an experimental British research aircraft built in the 1950s to investigate swept-wing and tailplane configurations that informed later high-speed fighter designs.
-
E.
Vickers Type 271 design studies
Vickers Type 271 design studies were early British aircraft design concepts by Vickers that formed the basis for the development of the Wellington Mk I bomber.
- F. None of above. chosen
Provenance (2 batches)
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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20d9d4c8190a2fd87f8a33c313d |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:32 p.m.