Triple
T13228055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz EQC |
E314931
|
entity |
| Predicate | acceleration0To100kmh |
P45714
|
FINISHED |
| Object | around 5.1 seconds (EQC 400 4MATIC) |
—
|
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.1 seconds (EQC 400 4MATIC) | Statement: [Mercedes-Benz EQC, acceleration0To100kmh, around 5.1 seconds (EQC 400 4MATIC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceleration0To100kmh Context triple: [Mercedes-Benz EQC, acceleration0To100kmh, around 5.1 seconds (EQC 400 4MATIC)]
-
A.
acceleration0To100Kmh
chosen
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.
0-200kmhTime
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 kilometers per hour.
-
D.
powerToWeightRatio
Indicates the relationship between an entity’s available power and its mass, expressing how much power is provided per unit of weight.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.