Triple
T31567690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-AMG S-Class Coupé (high-performance variants) |
E805462
|
entity |
| Predicate | exhaustNote |
P171965
|
FINISHED |
| Object | sporty AMG exhaust sound |
—
|
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: sporty AMG exhaust sound | Statement: [Mercedes-AMG S-Class Coupé (high-performance variants), exhaustNote, sporty AMG exhaust sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustNote Context triple: [Mercedes-AMG S-Class Coupé (high-performance variants), exhaustNote, sporty AMG exhaust sound]
-
A.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
C.
exhaustDirection
Indicates the direction in which exhaust gases or emissions are released or discharged from a source.
-
D.
органЭмиссии
Indicates the authority or body responsible for issuing or emitting something (such as a document, instrument, or asset).
-
E.
exhaustGasTemperature
Indicates the temperature of the exhaust gases produced by an engine or combustion process.
- F. None of above. chosen
Provenance (4 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:18 p.m.