Triple
T17326297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Model 82 design studies |
E420694
|
entity |
| Predicate | airframeTypeTarget |
P1524
|
FINISHED |
| Object | four‑engine turboprop transport |
—
|
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: four‑engine turboprop transport | Statement: [Lockheed Model 82 design studies, airframeTypeTarget, four‑engine turboprop transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airframeTypeTarget Context triple: [Lockheed Model 82 design studies, airframeTypeTarget, four‑engine turboprop transport]
-
A.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
B.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
-
C.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
D.
airframeConstruction
Indicates the method or structural approach used to build an aircraft’s main body and supporting framework.
-
E.
airWingType
Indicates the classification or category of an air wing associated with an entity.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d24e548190a766dd246a4d63d4 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.