Triple
T29154330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McLaren P1 |
E738994
|
entity |
| Predicate | acceleration0To200kmh |
P92950
|
FINISHED |
| Object | about 6.8 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: about 6.8 seconds | Statement: [McLaren P1, acceleration0To200kmh, about 6.8 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceleration0To200kmh Context triple: [McLaren P1, acceleration0To200kmh, about 6.8 seconds]
-
A.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
B.
acceleration0To60mph
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles per hour.
-
C.
accelerationTimeToTopSpeed
Indicates the duration required for something to increase its speed from an initial value to its maximum (top) speed.
-
D.
0-200kmhTime
chosen
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 kilometers 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662a87a6c8190b623bacb42af0097 |
completed | May 2, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:44 a.m.