Triple
T29018616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Silver Cloud I |
E737385
|
entity |
| Predicate | rideQuality |
P63555
|
FINISHED |
| Object | refined 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: refined ride | Statement: [Rolls-Royce Silver Cloud I, rideQuality, refined ride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideQuality Context triple: [Rolls-Royce Silver Cloud I, rideQuality, refined ride]
-
A.
rideFeature
chosen
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
B.
rideSystem
Indicates that one entity uses or travels on a transportation system or service provided by another entity.
-
C.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with another entity.
-
D.
rideStyle
Indicates the manner or characteristic way in which an entity rides or is ridden (e.g., in terms of technique, comfort, or behavior).
-
E.
rideType
Indicates the specific category or mode of transportation involved in a ride (e.g., standard, shared, premium).
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe293188190a510c1d54a2bf542 |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:47 a.m.