Triple

T24822247
Position Surface form Disambiguated ID Type / Status
Subject Successive Under-Relaxation E621091 entity
Predicate hasConstraintOnParameter P58313 FINISHED
Object 0 < omega < 1 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: 0 < omega < 1 | Statement: [Successive Under-Relaxation, hasConstraintOnParameter, 0 < omega < 1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConstraintOnParameter
Context triple: [Successive Under-Relaxation, hasConstraintOnParameter, 0 < omega < 1]
  • A. hasParameter
    Indicates that an entity is associated with a specific parameter that defines or constrains some aspect of its behavior, configuration, or characteristics.
  • B. hasConstraintArity
    Indicates that a constraint is associated with a specific number of arguments or elements it applies to.
  • C. hasConstraintOnSupport
    Indicates that one entity imposes a limitation, requirement, or condition on the type, amount, or manner of support that another entity can provide or receive.
  • D. hasParameterType
    Indicates that a parameter in a function, method, or operation is associated with a specific data type.
  • E. hasFormalConstraint chosen
    Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
  • 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_69e2fabfd4648190bd0e5c7f4dbb6cab completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6456608190b94e7c2e2c2a4824 completed May 2, 2026, 6:03 p.m.
Created at: April 18, 2026, 5:04 a.m.