Triple
T17682140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumley Lyster |
E440794
|
entity |
| Predicate | commanded |
P2333
|
FINISHED |
| Object | Royal Navy carrier air groups (World War II) |
—
|
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: Royal Navy carrier air groups (World War II) | Statement: [Lumley Lyster, commanded, Royal Navy carrier air groups (World War II)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Royal Navy carrier air groups (World War II) Context triple: [Lumley Lyster, commanded, Royal Navy carrier air groups (World War II)]
-
A.
Royal Navy carrier aircraft
Royal Navy carrier aircraft are fixed-wing planes and helicopters designed to operate from British aircraft carriers, conducting missions such as air defense, strike, reconnaissance, and anti-submarine warfare at sea.
-
B.
Royal Navy escort groups
Royal Navy escort groups were specialized World War II naval formations tasked with protecting Allied convoys and hunting enemy submarines in the Atlantic and surrounding waters.
-
C.
Royal Navy squadrons
Royal Navy squadrons were operational groupings of warships organized for specific tactical, strategic, or administrative purposes within the fleet.
-
D.
Royal Navy Hawker Sea Hawk carrier-based aircraft
The Royal Navy Hawker Sea Hawk was a British single-seat jet fighter used primarily as a carrier-based aircraft during the early Cold War era.
-
E.
Royal Navy Wildcat squadrons
Royal Navy Wildcat squadrons are helicopter units operating the AgustaWestland Wildcat for the Fleet Air Arm, providing maritime attack, reconnaissance, and support capabilities for Royal Navy operations.
- 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: Royal Navy carrier air groups (World War II) Target entity description: Royal Navy carrier air groups (World War II) were the naval aviation formations that operated from British aircraft carriers, conducting fighter, strike, and reconnaissance missions across major theaters of the Second World War.
-
A.
Royal Navy carrier aircraft
Royal Navy carrier aircraft are fixed-wing planes and helicopters designed to operate from British aircraft carriers, conducting missions such as air defense, strike, reconnaissance, and anti-submarine warfare at sea.
-
B.
Royal Navy escort groups
Royal Navy escort groups were specialized World War II naval formations tasked with protecting Allied convoys and hunting enemy submarines in the Atlantic and surrounding waters.
-
C.
Royal Navy squadrons
Royal Navy squadrons were operational groupings of warships organized for specific tactical, strategic, or administrative purposes within the fleet.
-
D.
Royal Navy Hawker Sea Hawk carrier-based aircraft
The Royal Navy Hawker Sea Hawk was a British single-seat jet fighter used primarily as a carrier-based aircraft during the early Cold War era.
-
E.
Royal Navy Wildcat squadrons
Royal Navy Wildcat squadrons are helicopter units operating the AgustaWestland Wildcat for the Fleet Air Arm, providing maritime attack, reconnaissance, and support capabilities for Royal Navy operations.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704514d481908aad4172fa930e6b |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:02 a.m.