Triple
T9817473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentley Continental GT Mulliner |
E238443
|
entity |
| Predicate | luxuryEmphasis |
P65476
|
FINISHED |
| Object | craftsmanship |
—
|
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: craftsmanship | Statement: [Bentley Continental GT Mulliner, luxuryEmphasis, craftsmanship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luxuryEmphasis Context triple: [Bentley Continental GT Mulliner, luxuryEmphasis, craftsmanship]
-
A.
isLuxuryHotel
Indicates that a hotel is classified as a luxury establishment, typically offering high-end amenities, services, and accommodations.
-
B.
luxMeans
Indicates that something serves as a means, method, or instrument by which a specified light-related effect, condition, or outcome is achieved.
-
C.
richIn
Indicates that something contains a high amount or concentration of a particular substance, quality, or resource.
-
D.
designEmphasizes
chosen
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
E.
elite
Indicates that the subject belongs to a select, superior, or highly privileged subset within a larger group or category.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f4a1548190a5afc5ee0d7da392 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:30 p.m.