Triple
T2470963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocket V8 engine |
E55370
|
entity |
| Predicate | combustionChamberType |
P4152
|
FINISHED |
| Object | overhead valve wedge-type |
—
|
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: overhead valve wedge-type | Statement: [Rocket V8 engine, combustionChamberType, overhead valve wedge-type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionChamberType Context triple: [Rocket V8 engine, combustionChamberType, overhead valve wedge-type]
-
A.
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.
-
B.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
C.
chamberType
chosen
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
-
D.
turbopumpType
Indicates the specific kind or classification of turbopump associated with an entity.
-
E.
chamberPressure
Indicates the pressure exerted by a gas or fluid within a defined chamber or enclosed space.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.