Triple

T6833222
Position Surface form Disambiguated ID Type / Status
Subject Successive Over-Relaxation E157387 entity
Predicate introducesParameter P12016 FINISHED
Object relaxation factor ω 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: relaxation factor ω | Statement: [Successive Over-Relaxation, introducesParameter, relaxation factor ω]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducesParameter
Context triple: [Successive Over-Relaxation, introducesParameter, relaxation factor ω]
  • A. parameter chosen
    Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
  • B. introducedPart
    Indicates that one entity has brought another entity into existence, use, or awareness as a component or element of something.
  • C. introduced
    Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
  • D. introducesSpeakerRole
    Indicates that one entity performs the act of presenting or announcing another entity in a specific speaker role.
  • E. canIntroduce
    Indicates that one entity has the ability or permission to introduce another entity to a third party or context.
  • 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_69c6882c53608190b99aebef079b23bd completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d62b1e8c8190a81d91191a54b073 completed March 27, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69c6d09d95f0819091ca7f897dc21efe completed March 27, 2026, 6:46 p.m.
Created at: March 27, 2026, 2:18 p.m.