Triple
T3714619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Trimotor (early variants) |
E81495
|
entity |
| Predicate | cockpitFeature |
P34590
|
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: [Ford Trimotor (early variants), cockpitFeature, enclosed cockpit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cockpitFeature Context triple: [Ford Trimotor (early variants), cockpitFeature, enclosed cockpit]
-
A.
flightDeckFeature
chosen
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
B.
cockpitType
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.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
E.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
- 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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc9ce253c8190ada8eaa395fd3d5c |
completed | March 8, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.