Triple
T2986403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric CF34-10E |
E80635
|
entity |
| Predicate | combustorType |
P31576
|
FINISHED |
| Object | annular combustor |
—
|
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: annular combustor | Statement: [General Electric CF34-10E, combustorType, annular combustor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustorType Context triple: [General Electric CF34-10E, combustorType, annular combustor]
-
A.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
B.
combustionChamber
chosen
Indicates that one entity functions as the combustion chamber in which another entity’s fuel–air mixture is burned to produce energy or propulsion.
-
C.
turbineType
Indicates the specific kind or category of turbine associated with or used by an entity.
-
D.
turbopumpType
Indicates the specific kind or classification of turbopump associated with an entity.
-
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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.