Triple
T4720654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kia Niro EV |
E104756
|
entity |
| Predicate | hasDriverAssistanceFeature |
P57273
|
FINISHED |
| Object | adaptive cruise control (available on many trims) |
—
|
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: adaptive cruise control (available on many trims) | Statement: [Kia Niro EV, hasDriverAssistanceFeature, adaptive cruise control (available on many trims)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriverAssistanceFeature Context triple: [Kia Niro EV, hasDriverAssistanceFeature, adaptive cruise control (available on many trims)]
-
A.
hasDriverAssistance
chosen
Indicates that an entity is equipped with or supports driver assistance features or systems.
-
B.
driveAssistFeature
Indicates that one entity provides an assistance feature that helps another entity perform driving-related tasks.
-
C.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
D.
hasParkFeature
Indicates that a park includes, contains, or is associated with a specific feature or amenity.
-
E.
isDriverless
Indicates that something operates or moves without a human driver controlling it.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.