Triple
T10037373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MX Brougham |
E205204
|
entity |
| Predicate | trimLevelType |
P83851
|
FINISHED |
| Object | Brougham-style luxury trim |
—
|
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: Brougham-style luxury trim | Statement: [MX Brougham, trimLevelType, Brougham-style luxury trim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimLevelType Context triple: [MX Brougham, trimLevelType, Brougham-style luxury trim]
-
A.
trimLevel
Indicates the specific configuration or package level of features or options applied to an item, typically distinguishing variants within the same base model.
-
B.
trimLevelAbove
Indicates that one entity’s trim level is higher or more upgraded than another’s.
-
C.
trimCharacteristic
chosen
Indicates that one entity defines or specifies a trimming-related property or feature of another entity.
-
D.
hasLevelType
Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
-
E.
offersTrimLevel
Indicates that a product or model is available in a specific trim level or configuration option.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcede428c8190ae115dc3425f9b0e |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.