Triple
T28807667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosch D-Jetronic |
E727422
|
entity |
| Predicate | fuelPressureRegulation |
P165600
|
FINISHED |
| Object | constant fuel pressure with return line |
—
|
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: constant fuel pressure with return line | Statement: [Bosch D-Jetronic, fuelPressureRegulation, constant fuel pressure with return line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelPressureRegulation Context triple: [Bosch D-Jetronic, fuelPressureRegulation, constant fuel pressure with return line]
-
A.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or system.
-
B.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
C.
hydraulicSystemPressure
Indicates the level of fluid pressure present within a hydraulic system during its operation.
-
D.
coolantPressure
Indicates the pressure level exerted by a coolant within a cooling system or component.
-
E.
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.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:29 a.m.