Triple
T30799026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-bucket |
E784313
|
entity |
| Predicate | typicalSuspension |
P156269
|
FINISHED |
| Object | solid front axle |
—
|
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: solid front axle | Statement: [T-bucket, typicalSuspension, solid front axle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSuspension Context triple: [T-bucket, typicalSuspension, solid front axle]
-
A.
typicalSuspensionCharacteristic
chosen
Indicates that something has a suspension property or behavior that is considered standard or characteristic for its type or context.
-
B.
suspensionType
Indicates the specific kind or configuration of suspension system associated with an entity (e.g., a vehicle or structure).
-
C.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
D.
suspensionMaterial
Indicates the material from which a suspension (such as a vehicle’s suspension component or system) is made.
-
E.
typicalTractionType
Indicates the usual or most common type of traction mechanism associated with an entity (such as how it is typically powered or driven).
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:42 p.m.