Triple
T6410622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eigg Electric |
E127694
|
entity |
| Predicate | hasBatteryStorageApprox |
P8443
|
FINISHED |
| Object | 100 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: 100 kWh | Statement: [Eigg Electric, hasBatteryStorageApprox, 100 kWh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBatteryStorageApprox Context triple: [Eigg Electric, hasBatteryStorageApprox, 100 kWh]
-
A.
hasInternalBattery
Indicates that one entity possesses a built-in power source contained within itself, rather than relying solely on external power.
-
B.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
C.
batteryCapacity
chosen
Indicates the amount of electrical energy a battery can store or deliver, typically expressed in units like mAh or Wh.
-
D.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
storesEnergyAs
Indicates that one entity retains or accumulates energy in the form or medium specified by another 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cf81508190bc09e58ec45bc858 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.