Triple
T30320404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi V8 |
E771181
|
entity |
| Predicate | luxuryFeature |
P168296
|
FINISHED |
| Object | leather upholstery |
—
|
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: leather upholstery | Statement: [Audi V8, luxuryFeature, leather upholstery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luxuryFeature Context triple: [Audi V8, luxuryFeature, leather upholstery]
-
A.
luxuryFeatures
chosen
Indicates that the subject possesses or is associated with high-end, premium, or upscale features beyond standard functionality.
-
B.
hasLoungeCar
Indicates that something includes or is equipped with a lounge car as part of its composition or configuration.
-
C.
luxurySegment
Indicates that the associated entity belongs to, targets, or is positioned within the luxury or premium market segment.
-
D.
customizableFeatures
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
E.
luxuryOrientation
Indicates a tendency or strategic focus toward luxury, premium, or high-end qualities, experiences, or positioning.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68197aac481909b701a91af7406e5 |
completed | May 2, 2026, 10:58 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:52 p.m.