Triple
T10092327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM T1 platform |
E215371
|
entity |
| Predicate | supportsWheelbaseVariants |
P92383
|
FINISHED |
| Object | standard wheelbase |
—
|
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: standard wheelbase | Statement: [GM T1 platform, supportsWheelbaseVariants, standard wheelbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWheelbaseVariants Context triple: [GM T1 platform, supportsWheelbaseVariants, standard wheelbase]
-
A.
wheelbaseVariantOf
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
B.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
C.
carTypeVariant
Indicates that one car type is a specific variant or version of another car type.
-
D.
wheelbaseClass
Indicates the classification of a vehicle based on the length or category of its wheelbase.
-
E.
wheelbaseSharedWith
Indicates that two vehicles have the same wheelbase dimensions or share a common wheelbase platform.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05c3c0c8190927580717429a4e5 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:01 p.m.