Triple
T1823994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM EcoTec3 V6 |
E40608
|
entity |
| Predicate | combustionType |
P31578
|
FINISHED |
| Object | spark-ignition |
—
|
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: spark-ignition | Statement: [GM EcoTec3 V6, combustionType, spark-ignition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionType Context triple: [GM EcoTec3 V6, combustionType, spark-ignition]
-
A.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
B.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
C.
propellantCombination
Indicates a specific pairing of propellant components that are used together in a propulsion or combustion system.
-
D.
turbineType
Indicates the specific kind or category of turbine associated with or used by an entity.
-
E.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
- F. None of above. chosen
Provenance (4 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab21ab83a48190a33afe5db19a21f8 |
completed | March 6, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61d97d008190b6642aef32eb7e36 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab21aa56108190a5123539d5020741 |
completed | March 6, 2026, 6:49 p.m. |
Created at: March 4, 2026, 7:32 p.m.