Triple
T17773265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NK-33 |
E443694
|
entity |
| Predicate | combustionMode |
P31578
|
FINISHED |
| Object | oxygen-rich |
—
|
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: oxygen-rich | Statement: [NK-33, combustionMode, oxygen-rich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionMode Context triple: [NK-33, combustionMode, oxygen-rich]
-
A.
combustionType
chosen
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
B.
combustionControl
Indicates a relationship where an entity regulates or manages the process, rate, or conditions of combustion in another entity or system.
-
C.
combustionProperty
Indicates a relationship where an entity is characterized by how it behaves in combustion, such as its flammability, ignition conditions, or burning behavior.
-
D.
combustionChamber
Indicates that one entity functions as the combustion chamber in which another entity’s fuel–air mixture is burned to produce energy or propulsion.
-
E.
isCombustionFree
Indicates that a process, device, or system operates without involving combustion or burning of fuel.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871a2130819081743ae89dddc64b |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.