Triple
T20634493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATTESA E-TS |
E507041
|
entity |
| Predicate | defaultDriveBias |
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: [ATTESA E-TS, defaultDriveBias, rear-wheel drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultDriveBias Context triple: [ATTESA E-TS, defaultDriveBias, rear-wheel drive]
-
A.
defaultDriver
Indicates that one entity is designated as the primary or standard driver for another entity (such as a vehicle or account).
-
B.
driveType
chosen
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
C.
typicalPositionBias
Indicates a systematic tendency for something to be placed, chosen, or interpreted in a commonly favored or default position relative to other options.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
SupdriveType
Indicates the specific category or classification of a Supdrive within its overall type system.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0e5fc481909e4f0dd7fb1203fc |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.