Triple
T29956013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Silver Seraph |
E760900
|
entity |
| Predicate | luxuryFeatures |
P168296
|
FINISHED |
| Object | hand-crafted interior |
—
|
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: hand-crafted interior | Statement: [Rolls-Royce Silver Seraph, luxuryFeatures, hand-crafted interior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luxuryFeatures Context triple: [Rolls-Royce Silver Seraph, luxuryFeatures, hand-crafted interior]
-
A.
customizableFeatures
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
B.
luxuryOrientation
Indicates a tendency or strategic focus toward luxury, premium, or high-end qualities, experiences, or positioning.
-
C.
luxurySegment
Indicates that the associated entity belongs to, targets, or is positioned within the luxury or premium market segment.
-
D.
hasLoungeCar
Indicates that something includes or is equipped with a lounge car as part of its composition or configuration.
-
E.
featureOfTrimLevels
Indicates that a particular feature is included in or associated with specific trim levels of a product or model.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6783a47d081909feed89b5b4017fb |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:27 p.m.