Triple
T28807669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosch D-Jetronic |
E727422
|
entity |
| Predicate | ignitionIntegration |
P165601
|
FINISHED |
| Object | separate ignition system |
—
|
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: separate ignition system | Statement: [Bosch D-Jetronic, ignitionIntegration, separate ignition system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ignitionIntegration Context triple: [Bosch D-Jetronic, ignitionIntegration, separate ignition system]
-
A.
chassisIntegrationWith
Indicates a relationship where one component or system is structurally or functionally integrated with a chassis as part of its overall assembly or design.
-
B.
vehicleIntegration
Indicates the relationship by which a system, component, or service is incorporated into and made to work cohesively with a vehicle’s hardware, software, or operational environment.
-
C.
controlIntegration
Indicates that one entity manages or coordinates the incorporation and interaction of another entity within a larger system or process.
-
D.
dieIntegration
Indicates that one entity is being integrated or combined into another system, structure, or context.
-
E.
integratesCapability
Indicates that one entity incorporates or combines another entity’s capability into its own functionality.
- 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.