Triple
T24801073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep Active Drive |
E620523
|
entity |
| Predicate | drivetrainModes |
P85075
|
FINISHED |
| Object | four-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: four-wheel drive | Statement: [Jeep Active Drive, drivetrainModes, four-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivetrainModes Context triple: [Jeep Active Drive, drivetrainModes, four-wheel drive]
-
A.
driveModes
chosen
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
B.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
drivetrainRole
Indicates the functional role or position an entity has within a drivetrain system (e.g., input, transmission, or output component).
-
D.
drivetrainCategory
Indicates the type or classification of a vehicle’s drivetrain system (e.g., FWD, RWD, AWD) associated with an entity.
-
E.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
- 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:49 a.m.