Triple
T881152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 96 |
E19028
|
entity |
| Predicate | rearSuspension |
P11926
|
FINISHED |
| Object | live axle with coil springs |
—
|
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: live axle with coil springs | Statement: [Saab 96, rearSuspension, live axle with coil springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rearSuspension Context triple: [Saab 96, rearSuspension, live axle with coil springs]
-
A.
suspensionRear
chosen
Indicates that the relationship or action involves the rear suspension component or system of an object, typically a vehicle.
-
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.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
E.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accb653c81909fe0753f78145be9 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.