Triple
T24800893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysler/Mitsubishi GS platform (first generation) |
E620518
|
entity |
| Predicate | underpinnedVehicle |
P128438
|
FINISHED |
| Object | Dodge Caliber |
—
|
NE NERFINISHED |
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: Dodge Caliber | Statement: [Chrysler/Mitsubishi GS platform (first generation), underpinnedVehicle, Dodge Caliber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underpinnedVehicle Context triple: [Chrysler/Mitsubishi GS platform (first generation), underpinnedVehicle, Dodge Caliber]
-
A.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
-
B.
intendedVehicle
Indicates that one entity is the vehicle that another entity plans or is meant to use.
-
C.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
-
D.
hasUndercarriageType
Indicates the specific type or configuration of undercarriage that an object (typically a vehicle or machine) possesses.
-
E.
basedOnVehicle
chosen
Indicates that one entity is derived from, modeled after, or otherwise conceptually or functionally based on a particular 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 18, 2026, 4:49 a.m.