Triple
T38318443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peugeot iOn |
E1033890
|
entity |
| Predicate | electricRangeWLTPApprox |
P59556
|
FINISHED |
| Object | around 100 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: around 100 km | Statement: [Peugeot iOn, electricRangeWLTPApprox, around 100 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricRangeWLTPApprox Context triple: [Peugeot iOn, electricRangeWLTPApprox, around 100 km]
-
A.
electricRangeWLTP
chosen
Indicates the maximum distance a vehicle can travel on electric power alone according to the WLTP test cycle.
-
B.
electricRange
Indicates the maximum distance an electrically powered device or vehicle can travel or operate solely on electric power before needing to recharge.
-
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.
electrificationCompatibility
Indicates whether one entity can be effectively and safely powered, charged, or operated using the electrical system, standards, or infrastructure associated with another entity.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.