Triple
T28341713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Evija |
E717831
|
entity |
| Predicate | 0To300KphTime |
P164418
|
FINISHED |
| Object | under 9 seconds |
—
|
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: under 9 seconds | Statement: [Lotus Evija, 0To300KphTime, under 9 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 0To300KphTime Context triple: [Lotus Evija, 0To300KphTime, under 9 seconds]
-
A.
0-200kmhTime
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 kilometers per hour.
-
B.
accelerationTimeToTopSpeed
Indicates the duration required for something to increase its speed from an initial value to its maximum (top) speed.
-
C.
category3UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of category 3 within a categorized scale.
-
D.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
E.
category2UpperBound_mph
Indicates the maximum speed in miles per hour that defines the upper limit of category 2 in a categorized range or scale.
- F. None of above. chosen
Provenance (4 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5645d48190b0c3a2bad5a2e539 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 12:40 a.m.