Triple
T15840101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet SS (VF Commodore-based) |
E384078
|
entity |
| Predicate | 0-60mphTimeApprox |
P8445
|
FINISHED |
| Object | about 4.5 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 4.5 seconds | Statement: [Chevrolet SS (VF Commodore-based), 0-60mphTimeApprox, about 4.5 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 0-60mphTimeApprox Context triple: [Chevrolet SS (VF Commodore-based), 0-60mphTimeApprox, about 4.5 seconds]
-
A.
acceleration0To60mph
chosen
Indicates the rate or time it takes for something to increase its speed from 0 to 60 miles 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.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
D.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
E.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.