Triple
T9603830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin-Baker MB 3 |
E231918
|
entity |
| Predicate | cockpitPosition |
P3544
|
FINISHED |
| Object | enclosed cockpit, mid-fuselage |
—
|
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, mid-fuselage | Statement: [Martin-Baker MB 3, cockpitPosition, enclosed cockpit, mid-fuselage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cockpitPosition Context triple: [Martin-Baker MB 3, cockpitPosition, enclosed cockpit, mid-fuselage]
-
A.
typicalPilotPosition
Indicates the usual or standard spatial position or placement where a pilot is located relative to the associated object or system.
-
B.
cockpitType
chosen
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
-
C.
cockpitCommonalityWith
Indicates that two aircraft or vehicle models share a similar or standardized cockpit layout, controls, or interface design.
-
D.
locationOnAircraft
Indicates that one entity is physically situated on or within an aircraft.
-
E.
fuselagePosition
Indicates the spatial placement or alignment of a fuselage relative to a reference frame or other aircraft components.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5cddf481909aa6b589bcb3e71a |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.