Triple
T14416833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Spectre |
E357473
|
entity |
| Predicate | targetRangeWLTP_miles |
P59556
|
FINISHED |
| Object | over 300 |
—
|
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: over 300 | Statement: [Rolls-Royce Spectre, targetRangeWLTP_miles, over 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetRangeWLTP_miles Context triple: [Rolls-Royce Spectre, targetRangeWLTP_miles, over 300]
-
A.
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.
-
B.
rangeNEDC
Indicates the driving range of a vehicle as measured under the New European Driving Cycle (NEDC) test procedure.
-
C.
electricRangeWLTP
chosen
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.
vehicleRestrictionMile
Indicates a restriction or limitation that applies to vehicles at a specific mile point or mile marker along a route.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:17 a.m.