Triple
T24546151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Super Sport |
E607231
|
entity |
| Predicate | typicalBrakeCharacteristic |
P109345
|
FINISHED |
| Object | larger or upgraded brakes |
—
|
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: larger or upgraded brakes | Statement: [Chevrolet Super Sport, typicalBrakeCharacteristic, larger or upgraded brakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBrakeCharacteristic Context triple: [Chevrolet Super Sport, typicalBrakeCharacteristic, larger or upgraded brakes]
-
A.
brakeFeature
chosen
Indicates that an entity possesses or is equipped with a particular braking-related feature or capability.
-
B.
brakeType
Indicates the specific kind or system of brakes associated with an entity.
-
C.
hasBraking
Indicates that an entity possesses or is equipped with a braking capability or braking system.
-
D.
brakingTestsPerformed
Indicates that one entity has carried out braking tests on another entity or system.
-
E.
brakeWear
Indicates that an entity is experiencing or exhibiting wear, degradation, or reduction in effectiveness of its braking components or braking function.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8c9ab9c81909ff56f707e3fd27b |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.