Triple
T28858621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEB platform |
E728801
|
entity |
| Predicate | wheelbaseAdjustable |
P92383
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MEB platform, wheelbaseAdjustable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelbaseAdjustable Context triple: [MEB platform, wheelbaseAdjustable, yes]
-
A.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
B.
wheelbaseComparedTo
Indicates a comparison between the distances between the front and rear wheel axles (wheelbases) of two entities, specifying how one wheelbase relates in size or length to the other.
-
C.
wheelbaseVariantOf
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
D.
supportsWheelbaseVariants
chosen
Indicates that one entity is compatible with or designed to accommodate multiple wheelbase length variants of another entity.
-
E.
steeringWheelType
Indicates the specific kind or design of steering wheel associated with an entity (such as a vehicle or driving setup).
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:46 a.m.