Triple
T34072960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Aero Engines |
E873822
|
entity |
| Predicate | designFeatureOfV2500 |
P57584
|
FINISHED |
| Object | high-bypass turbofan |
—
|
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: high-bypass turbofan | Statement: [International Aero Engines, designFeatureOfV2500, high-bypass turbofan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designFeatureOfV2500 Context triple: [International Aero Engines, designFeatureOfV2500, high-bypass turbofan]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
C.
featuresModel
Indicates that one entity includes, exposes, or is characterized by a particular model as one of its defining components or capabilities.
-
D.
V-213Features
Indicates that an entity possesses, exhibits, or is characterized by specific features or attributes.
-
E.
aircraftDesignFeature
Indicates a relationship where a specific design feature is associated with, or incorporated into, an aircraft.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 1:52 a.m.