Triple
T3560806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro RJX |
E75331
|
entity |
| Predicate | emissionsCharacteristic |
P8159
|
FINISHED |
| Object | intended to have lower emissions than BAe 146 |
—
|
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: intended to have lower emissions than BAe 146 | Statement: [Avro RJX, emissionsCharacteristic, intended to have lower emissions than BAe 146]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissionsCharacteristic Context triple: [Avro RJX, emissionsCharacteristic, intended to have lower emissions than BAe 146]
-
A.
emissionsControl
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
B.
emissionType
Indicates the specific category or kind of emission associated with an entity or activity.
-
C.
transportCharacteristic
chosen
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
D.
logisticalCharacteristic
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
E.
exhaustType
Indicates the specific kind or configuration of exhaust system 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08ac1b0819082021ecdd0061dc3 |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.