Triple
T26462157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT01 |
E665665
|
entity |
| Predicate | powerUnitConfiguration |
P167087
|
FINISHED |
| Object | 1.6 L V6 turbo hybrid |
—
|
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: 1.6 L V6 turbo hybrid | Statement: [AT01, powerUnitConfiguration, 1.6 L V6 turbo hybrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerUnitConfiguration Context triple: [AT01, powerUnitConfiguration, 1.6 L V6 turbo hybrid]
-
A.
powerUnitType
chosen
Indicates the type or category of power unit associated with or used by an entity.
-
B.
powerConversionSystem
Indicates a system that transforms electrical power from one form, level, or source into another to meet specific usage or distribution requirements.
-
C.
shaftPowerType
Indicates the type or category of power transmitted through a shaft in a mechanical or propulsion system.
-
D.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
E.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 12:13 a.m.