Triple
T36108062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EQA 300 4MATIC |
E1044416
|
entity |
| Predicate | batteryCapacityUsable |
P8443
|
FINISHED |
| Object | approximately 66.5 kWh |
—
|
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: approximately 66.5 kWh | Statement: [EQA 300 4MATIC, batteryCapacityUsable, approximately 66.5 kWh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batteryCapacityUsable Context triple: [EQA 300 4MATIC, batteryCapacityUsable, approximately 66.5 kWh]
-
A.
batteryCapacity
chosen
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
B.
batteryLife
Indicates how long a device can operate on a single charge or set of batteries before needing to be recharged or replaced.
-
C.
batteryPosition
Indicates the spatial placement or mounting location of a battery relative to another object or system.
-
D.
batteryVoltage
Indicates the electrical potential difference (voltage) provided by a battery in the context of the described relationship or system.
-
E.
bootCapacity
Indicates the storage volume or carrying capacity available in the boot (trunk) of a vehicle.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.