Triple
T10847101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V3 Supercharger |
E256040
|
entity |
| Predicate | canCharge |
P96049
|
FINISHED |
| Object | vehicle battery from low state of charge |
—
|
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: vehicle battery from low state of charge | Statement: [V3 Supercharger, canCharge, vehicle battery from low state of charge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCharge Context triple: [V3 Supercharger, canCharge, vehicle battery from low state of charge]
-
A.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
B.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
-
C.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
D.
supportsAutoCharge
Indicates that one entity enables or is compatible with automatic charging functionality for another entity.
-
E.
canHoldAdditionalChargeOf
Indicates that one entity has the capacity to store or accommodate an additional specified amount of electric charge beyond its current level.
- F. None of above. chosen
Provenance (4 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75113bc188190ac78df0c51d95de6 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.