Triple
T6510449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Edge |
E150113
|
entity |
| Predicate | rideCharacteristic |
P63555
|
FINISHED |
| Object | comfort-oriented 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: comfort-oriented ride | Statement: [Ford Edge, rideCharacteristic, comfort-oriented ride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideCharacteristic Context triple: [Ford Edge, rideCharacteristic, comfort-oriented ride]
-
A.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
B.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
C.
rideFeature
chosen
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
D.
transportationCharacteristic
Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
-
E.
rideModel
Indicates that one entity is a specific model or type designation of a ride associated with 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f398f10819096342f3646cefcc2 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.