Triple
T4403604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Theta platform |
E93673
|
entity |
| Predicate | usedForVehicleType |
P23423
|
FINISHED |
| Object | compact crossover SUV |
—
|
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: compact crossover SUV | Statement: [GM Theta platform, usedForVehicleType, compact crossover SUV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForVehicleType Context triple: [GM Theta platform, usedForVehicleType, compact crossover SUV]
-
A.
appliedToVehicleType
chosen
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
D.
vehicleUsed
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
E.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d1af608190ac06d50433cf24bb |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.