Triple
T17396676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safran Aircraft Engines |
E422971
|
entity |
| Predicate | designs |
P1529
|
FINISHED |
| Object | M88 |
—
|
NE NERFINISHED |
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: M88 | Statement: [Safran Aircraft Engines, designs, M88]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M88 Context triple: [Safran Aircraft Engines, designs, M88]
-
A.
M88
M88 is a bright spiral galaxy located in the constellation Coma Berenices and is one of the prominent members of the Virgo Cluster.
-
B.
M88
chosen
M88 is a French afterburning turbofan jet engine developed by Safran Aircraft Engines (formerly Snecma) to power the Dassault Rafale multirole fighter aircraft.
-
C.
M88-2
The M88-2 is a production variant of the Snecma M88 low-bypass turbofan engine used to power the Dassault Rafale multirole fighter aircraft.
-
D.
M88-3
M88-3 is an advanced variant of the Snecma M88 turbofan engine, developed to provide higher thrust and improved performance for modern fighter aircraft.
-
E.
M88-4E
The M88-4E is an upgraded variant of the Snecma M88 turbofan engine, offering improved reliability, durability, and performance for modern fighter aircraft.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abd9b748190bd55c863276d9e3a |
completed | April 19, 2026, 2:15 a.m. |
Created at: April 10, 2026, 5:45 a.m.