Triple
T16302942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyactiv-G engine |
E395834
|
entity |
| Predicate | engineeringApproach |
P49728
|
FINISHED |
| Object | holistic vehicle and powertrain integration |
—
|
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: holistic vehicle and powertrain integration | Statement: [Skyactiv-G engine, engineeringApproach, holistic vehicle and powertrain integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineeringApproach Context triple: [Skyactiv-G engine, engineeringApproach, holistic vehicle and powertrain integration]
-
A.
engineeringEmphasis
Indicates that something places a primary focus or specialization on engineering principles, methods, or activities.
-
B.
engineeringStandard
Indicates that something conforms to, is defined by, or is governed by a specified engineering standard or set of technical norms.
-
C.
engineeringGoal
chosen
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
D.
engineeringFeature
Indicates that one entity serves as an engineering-related feature, component, or characteristic of another entity within a technical or designed system.
-
E.
engineeringFeats
Indicates that one entity is recognized for notable engineering achievements, constructions, or technical accomplishments associated with another 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e3404288190a7106d62c15c3193 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.