Triple
T13525672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR |
E323010
|
entity |
| Predicate | usesPowertrainType |
P45712
|
FINISHED |
| Object | turbocharged 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: turbocharged petrol engines | Statement: [GR, usesPowertrainType, turbocharged petrol engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowertrainType Context triple: [GR, usesPowertrainType, turbocharged petrol engines]
-
A.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
-
B.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
-
C.
primaryPowertrain
chosen
Indicates the main powertrain system that primarily provides propulsion or drive power for a vehicle or machine.
-
D.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa6ad60819087824e4ac83934ed |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.