Triple
T13227969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | smart EQ forfour |
E314929
|
entity |
| Predicate | NEDCRange |
P8444
|
FINISHED |
| Object | approximately 155 km |
—
|
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: approximately 155 km | Statement: [smart EQ forfour, NEDCRange, approximately 155 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NEDCRange Context triple: [smart EQ forfour, NEDCRange, approximately 155 km]
-
A.
rangeNEDC
chosen
Indicates the driving range of a vehicle as measured under the New European Driving Cycle (NEDC) test procedure.
-
B.
hasDrivingRange
Indicates that an entity (such as a vehicle or device) has a specific maximum distance it can travel or operate on a given amount of energy or fuel.
-
C.
electricRangeWLTP
Indicates the maximum distance a vehicle can travel on electric power alone according to the WLTP test cycle.
-
D.
hasChargeRange
Indicates that an entity is associated with a minimum and maximum charge value defining the range of charge it can have or support.
-
E.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.