Triple
T14608640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLAR platform |
E342897
|
entity |
| Predicate | supportsSuspensionType |
P24486
|
FINISHED |
| Object | multi-link rear suspension |
—
|
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: multi-link rear suspension | Statement: [CLAR platform, supportsSuspensionType, multi-link rear suspension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSuspensionType Context triple: [CLAR platform, supportsSuspensionType, multi-link rear suspension]
-
A.
supportsSuspension
Indicates that one entity provides the necessary structure, strength, or mechanism to hold or keep another entity suspended.
-
B.
usesSuspensionFrom
Indicates that one entity employs or relies on a suspension derived from another entity as its source or basis.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
hasSuspension
Indicates that one entity is subject to a temporary suspension imposed or recorded by another entity.
-
E.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44d327c8190a8d20568429d0f80 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.