Triple
T34505681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3.3L Cyclone V6 |
E885878
|
entity |
| Predicate | driveTypeCompatibility |
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: [3.3L Cyclone V6, driveTypeCompatibility, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driveTypeCompatibility Context triple: [3.3L Cyclone V6, driveTypeCompatibility, rear-wheel drive]
-
A.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
busCompatibility
Indicates that two hardware or software components can operate together correctly over the same communication bus or interface.
-
C.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
-
D.
controlCarType
Indicates a relationship where an entity has authority to operate, manage, or make decisions about a specific type or category of car.
-
E.
usedByVehicleType
Indicates that something (such as a resource, component, or facility) is utilized or operated by a specific type or category of vehicle.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.