Triple
T13952332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BYD Seal |
E335559
|
entity |
| Predicate | hasFastCharging |
P5893
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BYD Seal, hasFastCharging, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFastCharging Context triple: [BYD Seal, hasFastCharging, true]
-
A.
fastChargingCapability
chosen
Indicates that an entity has the ability to charge at a higher-than-standard power rate, significantly reducing the time needed to reach a usable or full charge.
-
B.
fastChargingTime
Indicates the amount of time required to charge something (typically a battery or device) using a fast-charging method.
-
C.
supportsChargingStandard
Indicates that one entity is compatible with and able to operate using a specified charging standard defined by another entity.
-
D.
supportsChargingMethod
Indicates that one entity is compatible with and can operate using a specified charging method.
-
E.
supportsWirelessCharging
Indicates that one entity provides the capability for another entity to be charged without a physical wired connection, typically via inductive or similar wireless power transfer methods.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e146720819085d0f5eae558b7a4 |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.