Triple
T10284791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley Flying Spur Mulliner |
E241198
|
entity |
| Predicate | personalization |
P4599
|
FINISHED |
| Object | extensive bespoke options |
—
|
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: extensive bespoke options | Statement: [Bentley Flying Spur Mulliner, personalization, extensive bespoke options]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalization Context triple: [Bentley Flying Spur Mulliner, personalization, extensive bespoke options]
-
A.
personalGiftOf
Indicates that one entity has personally given another entity a gift, emphasizing a direct, individual act of gifting between them.
-
B.
custom
chosen
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
-
C.
primaryInteraction
Indicates the main or most significant interaction occurring between the involved entities.
-
D.
isPersonalTo
Indicates that something is uniquely associated with, belonging to, or intended for a specific individual, rather than being general or shared.
-
E.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:40 a.m.