Triple
T32974356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ducati superbike platform |
E843612
|
entity |
| Predicate | engineConfigurationIncludes |
P122598
|
FINISHED |
| Object | L-twin engines |
—
|
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: L-twin engines | Statement: [Ducati superbike platform, engineConfigurationIncludes, L-twin engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationIncludes Context triple: [Ducati superbike platform, engineConfigurationIncludes, L-twin engines]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
engineTypeIncluded
chosen
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
C.
combustionEngineConfiguration
Indicates the specific arrangement and setup of components and operating parameters within a combustion engine.
-
D.
tuningIncludes
Indicates that a particular tuning configuration or setup contains or encompasses another specified tuning element or component.
-
E.
engineModelOption
Indicates that a particular engine model is available as a configurable option for an item or product.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:22 a.m.