Triple
T21255501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi ASX |
E523857
|
entity |
| Predicate | drivingPosition |
P140177
|
FINISHED |
| Object | elevated |
—
|
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: elevated | Statement: [Mitsubishi ASX, drivingPosition, elevated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingPosition Context triple: [Mitsubishi ASX, drivingPosition, elevated]
-
A.
driverPosition
chosen
Indicates the spatial or role-based position of a driver relative to a vehicle or driving context.
-
B.
drivingFocus
Indicates that one entity serves as the primary motivating force, priority, or central concern guiding another entity’s actions or decisions.
-
C.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
D.
ridingPosition
Indicates the relative physical placement or posture of an entity while it is riding or being carried by another entity.
-
E.
drivingSide
Indicates which side of the road (left or right) vehicles are required to drive on in a given jurisdiction.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735a0e7dc8190b591b5b6786ce619 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:58 p.m.