Triple
T10325404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Ioniq 5 |
E242748
|
entity |
| Predicate | offersMotorConfiguration |
P45418
|
FINISHED |
| Object | single-motor rear-wheel drive |
—
|
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: single-motor rear-wheel drive | Statement: [Hyundai Ioniq 5, offersMotorConfiguration, single-motor rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersMotorConfiguration Context triple: [Hyundai Ioniq 5, offersMotorConfiguration, single-motor rear-wheel drive]
-
A.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
B.
offeredConfiguration
chosen
Indicates that one entity presents or makes available a specific configuration or setup option to another entity.
-
C.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
D.
offersBodyStyle
Indicates that an entity (such as a manufacturer or model line) makes a particular vehicle body style available as an option.
-
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cd76348190b93562112300acfc |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.