Triple
T29509325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Boxster (981) |
E748604
|
entity |
| Predicate | 0to100kmh |
P45714
|
FINISHED |
| Object | around 5.8 s for base model (with manual) |
—
|
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 5.8 s for base model (with manual) | Statement: [Porsche Boxster (981), 0to100kmh, around 5.8 s for base model (with manual)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 0to100kmh Context triple: [Porsche Boxster (981), 0to100kmh, around 5.8 s for base model (with manual)]
-
A.
acceleration0To100Kmh
chosen
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
B.
0-200kmhTime
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 kilometers per hour.
-
C.
acceleration0To300kmh
Indicates the rate or time it takes for something to increase its speed from 0 to 300 kilometers per hour.
-
D.
acceleration0To60mph
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
E.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c5d1cb48190867d8ce86724fb80 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:30 p.m.