Triple
T28651892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modularer Querbaukasten |
E725221
|
entity |
| Predicate | supportsPowertrains |
P40668
|
FINISHED |
| Object | petrol 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: petrol engines | Statement: [Modularer Querbaukasten, supportsPowertrains, petrol engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPowertrains Context triple: [Modularer Querbaukasten, supportsPowertrains, petrol engines]
-
A.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
B.
supportsDrivetrainFeature
chosen
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
C.
sharesPowertrainWith
Indicates that two entities use the same or a fundamentally identical powertrain system.
-
D.
primaryPowertrain
Indicates the main powertrain system that primarily provides propulsion or drive power for a vehicle or machine.
-
E.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: April 28, 2026, 4:52 a.m.