Triple

T29706224
Position Surface form Disambiguated ID Type / Status
Subject McLaren Artura E751635 entity
Predicate electricCharging P194517 FINISHED
Object AC charging via plug-in port 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: AC charging via plug-in port | Statement: [McLaren Artura, electricCharging, AC charging via plug-in port]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electricCharging
Context triple: [McLaren Artura, electricCharging, AC charging via plug-in port]
  • A. chargingLocation
    Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
  • B. 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.
  • C. chargingNetworkCompatibility
    Indicates that one entity’s charging system is compatible with, and can be used on, another entity’s charging network.
  • D. chargingModel
    Indicates the pricing or billing scheme applied to an entity, such as how costs are calculated or charged.
  • E. chargingZone
    Indicates a designated area or zone where charging (typically of vehicles or devices) is permitted or intended to occur.
  • 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_69f0d62748848190b030d0a703629a7d completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd783fed9c81909e792702636c4f1f completed May 8, 2026, 5:44 a.m.
PD Predicate disambiguation batch_69fd7788e63c81909de22fdafcfe41c0 completed May 8, 2026, 5:41 a.m.
PDg Predicate description generation batch_69fd783e9e5c819087dec7fefa03700d completed May 8, 2026, 5:44 a.m.
Created at: April 28, 2026, 7:27 p.m.