Triple
T4720638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kia Niro EV |
E104756
|
entity |
| Predicate | batteryCapacityOption |
P8443
|
FINISHED |
| Object | 39.2 kWh (approximate usable) |
—
|
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: 39.2 kWh (approximate usable) | Statement: [Kia Niro EV, batteryCapacityOption, 39.2 kWh (approximate usable)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryCapacityOption Context triple: [Kia Niro EV, batteryCapacityOption, 39.2 kWh (approximate usable)]
-
A.
batteryCapacity
chosen
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
B.
batteryType
Indicates the specific kind or category of battery associated with or used by an entity.
-
C.
bootCapacity
Indicates the storage volume or carrying capacity available in the boot (trunk) of a vehicle.
-
D.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
E.
plannedMainBatteryConfiguration
Indicates the intended or designed primary weapon or main battery setup that was planned for an entity, typically before implementation or construction.
- 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.