Triple
T4720660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kia Niro EV |
E104756
|
entity |
| Predicate | hasDigitalInstrumentCluster |
P8110
|
FINISHED |
| Object | 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: available on many trims | Statement: [Kia Niro EV, hasDigitalInstrumentCluster, available on many trims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalInstrumentCluster Context triple: [Kia Niro EV, hasDigitalInstrumentCluster, available on many trims]
-
A.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
B.
hasOnboardComputer
chosen
Indicates that one entity is equipped with or contains an onboard computer system.
-
C.
hasPassengerInformationSystem
Indicates that an entity is equipped with a system that provides information to passengers, such as schedules, announcements, or travel updates.
-
D.
hasDriverAssistance
Indicates that an entity is equipped with or supports driver assistance features or systems.
-
E.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
- 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_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.