Triple
T34178652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isuzu Faster pickup platform |
E876747
|
entity |
| Predicate | optionalDriveConfiguration |
P4169
|
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: [Isuzu Faster pickup platform, optionalDriveConfiguration, four‑wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalDriveConfiguration Context triple: [Isuzu Faster pickup platform, optionalDriveConfiguration, four‑wheel drive]
-
A.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
-
B.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
C.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
E.
hasCarConfiguration
Indicates that an entity is associated with a specific car configuration, detailing how the car is set up or specified.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7100315948190bc23da7543715446 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.