Triple

T26966730
Position Surface form Disambiguated ID Type / Status
Subject RP E679190 entity
Predicate errorDirection P162013 FINISHED
Object may reject some yes-instances with bounded probability 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: may reject some yes-instances with bounded probability | Statement: [RP, errorDirection, may reject some yes-instances with bounded probability]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: errorDirection
Context triple: [RP, errorDirection, may reject some yes-instances with bounded probability]
  • A. errorDirection
    Indicates the direction or orientation in which an error or deviation occurs relative to a reference or expected value.
  • B. errorSide
    Indicates the side, party, or component on which an error occurs or is attributed in a given context.
  • C. offsetDirection
    Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
  • D. errorTerm
    Indicates the specific discrepancy or residual value that quantifies the difference between an observed outcome and its predicted or true value in a model or calculation.
  • E. errorOn
    Indicates that one entity experiences, produces, or is associated with an error in relation to another entity 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_69eeeb4f3a448190b1e94b2d4776c16e completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f63639a84c81909d700a539b458b42 completed May 2, 2026, 5:36 p.m.
PD Predicate disambiguation batch_69f631850ae08190a0ba51e4f1e4ccb3 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 6:36 a.m.