Triple
T19045780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferrari SF90 Stradale |
E466126
|
entity |
| Predicate | electricDriveMode |
P85075
|
FINISHED |
| Object | eDrive mode for electric-only operation |
—
|
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: eDrive mode for electric-only operation | Statement: [Ferrari SF90 Stradale, electricDriveMode, eDrive mode for electric-only operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricDriveMode Context triple: [Ferrari SF90 Stradale, electricDriveMode, eDrive mode for electric-only operation]
-
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.
electricMotorType
Indicates the specific kind or category of electric motor associated with an entity.
-
C.
hasElectricMotor
Indicates that an entity is equipped with, contains, or uses an electric motor as part of its operation or structure.
-
D.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
E.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d80466f88190988171920f2be7dc |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.