Triple
T402791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supermarine Spiteful |
E9320
|
entity |
| Predicate | cockpit |
P3544
|
FINISHED |
| Object | enclosed cockpit |
—
|
LITERAL FINISHED |
How this triple was built (2 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: enclosed cockpit | Statement: [Supermarine Spiteful, cockpit, enclosed cockpit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cockpit Context triple: [Supermarine Spiteful, cockpit, enclosed cockpit]
-
A.
cockpitType
chosen
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
-
B.
avionics
Indicates that an entity is related to the electronic systems used to control, monitor, or assist the operation of aircraft or spacecraft.
-
C.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
D.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
E.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
- F. None of above.
Provenance (3 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca0e2048190a7bf360257965e56 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96ee4ec8190a5c0e3f491d3963d |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.