Triple
T36437488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelby GT500 (2020–2022) |
E897626
|
entity |
| Predicate | CarbonFiberTrackPackFeatures |
P185499
|
FINISHED |
| Object | carbon fiber wheels |
—
|
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: carbon fiber wheels | Statement: [Shelby GT500 (2020–2022), CarbonFiberTrackPackFeatures, carbon fiber wheels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CarbonFiberTrackPackFeatures Context triple: [Shelby GT500 (2020–2022), CarbonFiberTrackPackFeatures, carbon fiber wheels]
-
A.
gForce
Indicates the gravitational or inertial acceleration experienced by an object, typically expressed as a multiple of standard gravity.
-
B.
racingModel
Indicates that one entity is a specific model or version designed or configured for racing in relation to another entity.
-
C.
carbodyMaterial
Indicates the material from which a vehicle’s body or main structural shell is made.
-
D.
hasRacingSide
Indicates that an entity possesses or is associated with a side or aspect specifically dedicated to racing.
-
E.
chassisConstruction
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
- F. None of above. chosen
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. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.