Triple

T3245852
Position Surface form Disambiguated ID Type / Status
Subject Magnuson–Moss Warranty Act provisions E68064 entity
Predicate setMinimumValue P46803 FINISHED
Object $10 for products covered 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: $10 for products covered | Statement: [Magnuson–Moss Warranty Act provisions, setMinimumValue, $10 for products covered]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: setMinimumValue
Context triple: [Magnuson–Moss Warranty Act provisions, setMinimumValue, $10 for products covered]
  • A. hasMinimumValue
    Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
  • B. isMinimumWhen
    Indicates that a value or state is at its smallest or least level precisely under certain specified conditions or circumstances.
  • C. minimumWidth
    Indicates that there is a specified smallest allowable or required width for something in the relationship.
  • D. setsMaximum
    Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
  • E. minimumNumber
    Indicates that the associated value is the smallest or least quantity allowed, required, or observed within a given set or context.
  • 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_69ad858e4c708190aa31d486cfee8a6a completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaf1a96148190b63bf46209712707 completed March 8, 2026, 5:17 p.m.
PD Predicate disambiguation batch_69ada41837e48190933572165be0ca38 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada525bb2c8190b773efe6d696b6ab completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:09 p.m.