Triple

T26006749
Position Surface form Disambiguated ID Type / Status
Subject Euclidean algorithm for polynomials E646780 entity
Predicate finalNonzeroRemainderIs P170943 FINISHED
Object greatest common divisor 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: greatest common divisor | Statement: [Euclidean algorithm for polynomials, finalNonzeroRemainderIs, greatest common divisor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalNonzeroRemainderIs
Context triple: [Euclidean algorithm for polynomials, finalNonzeroRemainderIs, greatest common divisor]
  • A. hasRemainderTo
    Indicates that one quantity leaves a specified remainder when divided by another quantity.
  • B. isNonzeroFor
    Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
  • C. isNonZeroBecause
    Indicates that a value is non-zero specifically due to the stated cause, reason, or contributing factor.
  • D. isNonzeroIf
    Indicates that one quantity is guaranteed to be nonzero whenever a specified condition or related quantity holds or is nonzero.
  • E. isZeroFor
    Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified 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_69e77e89d5848190b54352cdb74f6029 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f6984bb55c8190862eb8796868d188 completed May 3, 2026, 12:35 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
PDg Predicate description generation batch_69f6978ec27c8190a488e1f9c2566d38 completed May 3, 2026, 12:32 a.m.
Created at: April 22, 2026, 9 a.m.