Triple

T34645486
Position Surface form Disambiguated ID Type / Status
Subject V2 Supercharger E889682 entity
Predicate hasLowerMaxPowerThan P198424 FINISHED
Object V3 Supercharger NE NERFINISHED

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: V3 Supercharger | Statement: [V2 Supercharger, hasLowerMaxPowerThan, V3 Supercharger]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLowerMaxPowerThan
Context triple: [V2 Supercharger, hasLowerMaxPowerThan, V3 Supercharger]
  • A. hasLowerPowerConsumptionThan
    Indicates that one entity uses less power or energy than another entity under comparable conditions.
  • B. hasLowPowerVariant
    Indicates that an entity has a related version or configuration designed to operate with reduced power consumption compared to the standard one.
  • C. hasLowerThroughputThan
    Indicates that one entity’s throughput is less than that of another entity.
  • D. hasLowerDensityThan
    Indicates that one entity has a lower density (mass per unit volume) compared to another entity.
  • E. reducedPowerOf
    Indicates that one entity has a diminished or weakened level of power, authority, or effectiveness relative to another or to its previous state.
  • 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_69f349d825c88190bfc6170ac9281260 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fee25dbca481909e6f1c255122b3a8 completed May 9, 2026, 7:29 a.m.
PD Predicate disambiguation batch_69fee1c8915c8190b08b63e42881f1a9 completed May 9, 2026, 7:27 a.m.
PDg Predicate description generation batch_69fee25c7c548190a2c6e50074a33da4 completed May 9, 2026, 7:29 a.m.
Created at: May 1, 2026, 2:04 a.m.