Triple
T13563071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSA EMP2 platform (later generations) |
E323958
|
entity |
| Predicate | supportsWheelbaseVariation |
P92383
|
FINISHED |
| Object | short 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: short wheelbase | Statement: [PSA EMP2 platform (later generations), supportsWheelbaseVariation, short wheelbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWheelbaseVariation Context triple: [PSA EMP2 platform (later generations), supportsWheelbaseVariation, short wheelbase]
-
A.
supportsWheelbaseVariants
chosen
Indicates that one entity is compatible with or designed to accommodate multiple wheelbase length variants of another entity.
-
B.
wheelbaseVariantOf
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
C.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
D.
wheelbaseSharedWith
Indicates that two vehicles have the same wheelbase dimensions or share a common wheelbase platform.
-
E.
wheelbaseClass
Indicates the classification of a vehicle based on the length or category of its wheelbase.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.