Triple
T10345302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce AE 3007A1/3 |
E243728
|
entity |
| Predicate | emissionsCategory |
P46939
|
FINISHED |
| Object | turbofan jet engine |
—
|
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: turbofan jet engine | Statement: [Rolls-Royce AE 3007A1/3, emissionsCategory, turbofan jet engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionsCategory Context triple: [Rolls-Royce AE 3007A1/3, emissionsCategory, turbofan jet engine]
-
A.
emissionType
chosen
Indicates the specific category or kind of emission associated with an entity or activity.
-
B.
emissionsControl
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
C.
hasCarbonFootprintCategory
Indicates that an entity is associated with a specific classification of its carbon footprint level or impact.
-
D.
hasPersistentGasEmissions
Indicates that an entity continuously or repeatedly releases gaseous substances over an extended period.
-
E.
hasEnvironmentalImpactType
Indicates that something affects the environment in a specific way categorized by a particular type of impact.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e923e3d08190971073ce41ff860f |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:56 a.m.