Triple
T33041717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strensham services |
E845483
|
entity |
| Predicate | hasElectricVehicleCharging |
P44374
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Strensham services, hasElectricVehicleCharging, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricVehicleCharging Context triple: [Strensham services, hasElectricVehicleCharging, yes]
-
A.
chargingNetworkCompatibility
Indicates that one entity’s charging system is compatible with, and can be used on, another entity’s charging network.
-
B.
chargingLocation
chosen
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
-
C.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
haveElectricChargePattern
Indicates that an entity possesses a specific configuration or distribution of electric charge.
-
E.
fastChargingCapability
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.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 1:24 a.m.