Triple
T13409071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbomeca Aubisque |
E320039
|
entity |
| Predicate | thrustGenerationMethod |
P69703
|
FINISHED |
| Object | high-velocity exhaust jet |
—
|
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-velocity exhaust jet | Statement: [Turbomeca Aubisque, thrustGenerationMethod, high-velocity exhaust jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustGenerationMethod Context triple: [Turbomeca Aubisque, thrustGenerationMethod, high-velocity exhaust jet]
-
A.
thrustClass
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
B.
generationMethod
chosen
Indicates the process, technique, or procedure by which something is created, produced, or derived.
-
C.
thrustDistribution
Indicates how thrust or propulsive force is apportioned or spread among different components, directions, or stages within a system.
-
D.
signalGenerationMethod
Indicates the method or technique used to produce or generate a signal in a given context.
-
E.
thrustAugmentationMethod
Indicates the method or technique used to increase or enhance thrust in a propulsion system.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4d2c5481908facfaaa1501e344 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.