Triple
T16302684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyactiv technology |
E395829
|
entity |
| Predicate | engineTypeIncluded |
P122598
|
FINISHED |
| Object | high-compression gasoline engine |
—
|
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: high-compression gasoline engine | Statement: [Skyactiv technology, engineTypeIncluded, high-compression gasoline engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineTypeIncluded Context triple: [Skyactiv technology, engineTypeIncluded, high-compression gasoline engine]
-
A.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
D.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
E.
engineUsedIn
Indicates that a particular engine is utilized as a component or power source within a specified system, device, or application.
- 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_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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.