Triple
T36116388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Multi-purpose Vehicle |
E1044624
|
entity |
| Predicate | driveLayoutOptions |
P4169
|
FINISHED |
| Object | rear-wheel drive |
—
|
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: rear-wheel drive | Statement: [International Multi-purpose Vehicle, driveLayoutOptions, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveLayoutOptions Context triple: [International Multi-purpose Vehicle, driveLayoutOptions, rear-wheel drive]
-
A.
driveLayoutSupported
Indicates that a particular drive layout or configuration is compatible with and can be correctly handled by a given system or component.
-
B.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
driveScheme
Indicates that one entity operates or controls a scheme, system, or initiative, causing it to function or move forward.
-
D.
driveModes
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
E.
vehicleLayout
Indicates how the components or seating within a vehicle are arranged or configured relative to each other.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:08 p.m.