Triple
T14416851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce electric models |
E357473
|
entity |
| Predicate | drivingExperienceGoal |
P114172
|
FINISHED |
| Object | near-silent ride |
—
|
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: near-silent ride | Statement: [Rolls-Royce electric models, drivingExperienceGoal, near-silent ride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingExperienceGoal Context triple: [Rolls-Royce electric models, drivingExperienceGoal, near-silent ride]
-
A.
drivingExperience
Indicates the extent or history of a person's involvement in driving vehicles, typically measured by duration, frequency, or level of skill.
-
B.
hasDrivingSkill
Indicates that an entity possesses the ability or competence to operate and control a vehicle.
-
C.
drivingChallenge
Indicates a situation in which driving is made difficult or demanding due to conditions, obstacles, or required skills.
-
D.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
E.
drivingExperienceBooking
Indicates that an entity books or reserves a driving experience activity for themselves or someone else.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cec8e4819087c72d82f9caacda |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:17 a.m.