Triple
T14011915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-AMG S 63 |
E337101
|
entity |
| Predicate | hasPerformanceBranding |
P48662
|
FINISHED |
| Object | AMG badging |
—
|
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: AMG badging | Statement: [Mercedes-AMG S 63, hasPerformanceBranding, AMG badging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceBranding Context triple: [Mercedes-AMG S 63, hasPerformanceBranding, AMG badging]
-
A.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
B.
hasBrandIdentityElement
chosen
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
C.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
D.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
-
E.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed5cfd0819085b9c860b119a9de |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.