Triple
T36437467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelby GT500 (2020–2022) |
E897626
|
entity |
| Predicate | dampers |
P49705
|
FINISHED |
| Object | MagneRide adaptive dampers |
E42277
|
NE 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: MagneRide adaptive dampers | Statement: [Shelby GT500 (2020–2022), dampers, MagneRide adaptive dampers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dampers Context triple: [Shelby GT500 (2020–2022), dampers, MagneRide adaptive dampers]
-
A.
dampingType
chosen
Indicates the specific kind or method of damping applied in a system or interaction between entities.
-
B.
hasTunedMassDamper
Indicates that an entity is equipped with or incorporates a tuned mass damper as part of its structure or system.
-
C.
tunedMassDamperWeight_tonnes
Indicates the weight, measured in metric tonnes, of the tuned mass damper used in a structure or system.
-
D.
pumps
Indicates that one entity moves or circulates a substance (such as a fluid or gas) into, out of, or through another entity using pressure or mechanical action.
-
E.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
- F. None of above.
Provenance (4 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c418376481909c4dd8d68b1f44ee |
completed | June 22, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.