Triple

T28900212
Position Surface form Disambiguated ID Type / Status
Subject DIN 41612 E732931 entity
Predicate hasCurrentRating P184596 FINISHED
Object typically up to several amperes per contact (type-dependent) 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: typically up to several amperes per contact (type-dependent) | Statement: [DIN 41612, hasCurrentRating, typically up to several amperes per contact (type-dependent)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCurrentRating
Context triple: [DIN 41612, hasCurrentRating, typically up to several amperes per contact (type-dependent)]
  • A. hasRatingLevel
    Indicates that an entity is associated with a particular rating level or score category.
  • B. hasScoreAvailable
    Indicates that a score or rating for the relevant entity is present and can be accessed.
  • C. hasRatingFocus
    Indicates that an entity’s primary emphasis or concern is on ratings, such as scores, reviews, or evaluative metrics.
  • D. hasRankingPoints
    Indicates that an entity possesses a certain number of ranking points used to determine its position or standing within a ranking system.
  • E. isHumanRated
    Indicates that something has been evaluated and approved as safe or suitable for use by humans.
  • 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_69f05b08c2008190ac426a035a2ed66d completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f7b365288c8190bcb11fcfba028737 completed May 3, 2026, 8:43 p.m.
PD Predicate disambiguation batch_69f7b1b8a9fc8190a1279e67a2d12707 completed May 3, 2026, 8:36 p.m.
PDg Predicate description generation batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d completed May 3, 2026, 8:41 p.m.
Created at: April 28, 2026, 8:02 a.m.