Triple

T12207453
Position Surface form Disambiguated ID Type / Status
Subject Wasserstein GAN E290870 entity
Predicate enforcesLipschitzConstraintBy P49586 FINISHED
Object weight clipping 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: weight clipping | Statement: [Wasserstein GAN, enforcesLipschitzConstraintBy, weight clipping]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: enforcesLipschitzConstraintBy
Context triple: [Wasserstein GAN, enforcesLipschitzConstraintBy, weight clipping]
  • A. constrainedBy
    Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
  • B. designedToConstrain chosen
    Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
  • C. regularizationControlledBy
    Indicates that the regularization applied in a process, model, or system is governed, adjusted, or determined by a specific controlling factor or mechanism.
  • D. hasFormalConstraint
    Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
  • E. enforcedOn
    Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
  • 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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d920e312708190b4aede2e21f5f697 completed April 10, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69d91c3d669c81908eea7ad61122d275 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:51 p.m.