Triple
T13503073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar I-Pace |
E320940
|
entity |
| Predicate | EPACombinedRange_miles |
P75784
|
FINISHED |
| Object | around 234 |
—
|
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 234 | Statement: [Jaguar I-Pace, EPACombinedRange_miles, around 234]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EPACombinedRange_miles Context triple: [Jaguar I-Pace, EPACombinedRange_miles, around 234]
-
A.
rangeNEDC
Indicates the driving range of a vehicle as measured under the New European Driving Cycle (NEDC) test procedure.
-
B.
hasDrivingRange
chosen
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.
fuelEfficiency
Indicates how effectively an entity uses fuel to perform a given amount of work or travel a certain distance.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf810e248190a060481004503f96 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.