Triple
T10154474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ducati Streetfighter |
E232737
|
entity |
| Predicate | hasRearBrakeType |
P4166
|
FINISHED |
| Object | single disc brake |
—
|
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: single disc brake | Statement: [Ducati Streetfighter, hasRearBrakeType, single disc brake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRearBrakeType Context triple: [Ducati Streetfighter, hasRearBrakeType, single disc brake]
-
A.
brakeType
chosen
Indicates the specific kind or system of brakes associated with an entity.
-
B.
isOnRearPlate
Indicates that one entity is positioned on or attached to the rear plate of another entity.
-
C.
suspensionRear
Indicates that the relationship or action involves the rear suspension component or system of an object, typically a vehicle.
-
D.
hasUndercarriageType
Indicates the specific type or configuration of undercarriage that an object (typically a vehicle or machine) possesses.
-
E.
bogieType
Indicates the specific configuration or classification of a vehicle’s bogie (wheel assembly) used in its design or operation.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec38f594819088a7eb73fc25feff |
completed | April 2, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:08 p.m.