Triple
T13425997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opel Rocks-e |
E313483
|
entity |
| Predicate | rangeWLTP |
P59556
|
FINISHED |
| Object | approximately 75 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 75 km | Statement: [Opel Rocks-e, rangeWLTP, approximately 75 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeWLTP Context triple: [Opel Rocks-e, rangeWLTP, approximately 75 km]
-
A.
rangeNEDC
Indicates the driving range of a vehicle as measured under the New European Driving Cycle (NEDC) test procedure.
-
B.
electricRangeWLTP
chosen
Indicates the maximum distance a vehicle can travel on electric power alone according to the WLTP test cycle.
-
C.
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.
-
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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.