Triple
T35757982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosch mechanical fuel injection |
E1033497
|
entity |
| Predicate | actuation |
P140753
|
FINISHED |
| Object | cam-driven |
—
|
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: cam-driven | Statement: [Bosch mechanical fuel injection, actuation, cam-driven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuation Context triple: [Bosch mechanical fuel injection, actuation, cam-driven]
-
A.
usesActuation
Indicates that one entity employs or applies a particular actuation method, mechanism, or system to perform its function or achieve an effect.
-
B.
actuatedBy
chosen
Indicates that an action, process, or mechanism is initiated, driven, or controlled by a specific agent or cause.
-
C.
physicalAction
Indicates a relationship where one entity performs or undergoes a tangible, bodily movement or interaction in the physical world.
-
D.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
E.
act
Indicates the performance or execution of an action or behavior by an entity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.