Triple
T27507677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotax 914F |
E694321
|
entity |
| Predicate | turbochargerControl |
P162463
|
FINISHED |
| Object | automatic wastegate control |
—
|
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: automatic wastegate control | Statement: [Rotax 914F, turbochargerControl, automatic wastegate control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turbochargerControl Context triple: [Rotax 914F, turbochargerControl, automatic wastegate control]
-
A.
turbochargerType
Indicates the specific kind or classification of turbocharger associated with an engine or system.
-
B.
hasTurbocharger
Indicates that an engine or vehicle is equipped with a turbocharger that boosts its air intake and performance.
-
C.
turbochargedVariant
Indicates that one entity is a turbocharged version or configuration of another entity.
-
D.
valvetrainControl
Indicates a control relationship in which one entity regulates or manages the operation of an engine’s valvetrain system.
-
E.
turbochargedEngineAvailable
Indicates that a turbocharged engine option is offered or can be equipped for the given vehicle or model.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef65ca88190b3e3b1c91d668843 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:14 p.m.