Triple
T20027229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa DNA driving mode selector |
E495015
|
entity |
| Predicate | hasDrivingMode |
P85075
|
FINISHED |
| Object | Dynamic |
—
|
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: Dynamic | Statement: [Alfa DNA driving mode selector, hasDrivingMode, Dynamic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingMode Context triple: [Alfa DNA driving mode selector, hasDrivingMode, Dynamic]
-
A.
hasDrivingStyle
Indicates the characteristic manner or pattern in which an entity typically drives.
-
B.
driveModes
chosen
Indicates that an entity (such as a vehicle or device) supports or operates in one or more specific driving or operational modes.
-
C.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
D.
hasTrafficMode
Indicates the mode or type of traffic associated with or applicable to an entity (e.g., pedestrian, vehicular, public transit).
-
E.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628e1eec81908e4c9b2b0b68f0e4 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.