Triple
T30234464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi S3 |
E768720
|
entity |
| Predicate | typical0To100Kmh |
P45714
|
FINISHED |
| Object | around 4.5–6.0 seconds depending on generation |
—
|
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 4.5–6.0 seconds depending on generation | Statement: [Audi S3, typical0To100Kmh, around 4.5–6.0 seconds depending on generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typical0To100Kmh Context triple: [Audi S3, typical0To100Kmh, around 4.5–6.0 seconds depending on generation]
-
A.
typicalTopSpeedRange
Indicates the usual range of maximum speeds that an entity is capable of under normal conditions.
-
B.
acceleration0To100Kmh
chosen
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
C.
typicalSpeedEnvironment
Indicates that an environment is characterized by a particular speed that is typical or normal for it.
-
D.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
E.
0-200kmhTime
Indicates the time it takes for something, typically a vehicle, to accelerate from 0 to 200 kilometers per hour.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:37 p.m.