Triple
T38055032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breguet 941 |
E949876
|
entity |
| Predicate | liftEnhancementMethod |
P106975
|
FINISHED |
| Object | propulsive blown flaps |
—
|
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: propulsive blown flaps | Statement: [Breguet 941, liftEnhancementMethod, propulsive blown flaps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liftEnhancementMethod Context triple: [Breguet 941, liftEnhancementMethod, propulsive blown flaps]
-
A.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
maximumEnhancementFactor
Indicates the highest degree to which something can be increased, amplified, or improved by a given process or factor.
-
C.
enhancementSource
chosen
Indicates that one entity serves as the origin or provider of an enhancement, improvement, or upgrade applied to another entity.
-
D.
upgradeEffect
Indicates that one entity causes an improvement or enhancement in the capabilities, performance, or status of another entity.
-
E.
usesChainLift
Indicates that one entity employs a chain lift mechanism to move or elevate another 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.