Triple

T29968867
Position Surface form Disambiguated ID Type / Status
Subject Gentzen’s consistency proof for arithmetic E761263 entity
Predicate usesOrdinal P92648 FINISHED
Object epsilon_0 (ε₀) 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: epsilon_0 (ε₀) | Statement: [Gentzen’s consistency proof for arithmetic, usesOrdinal, epsilon_0 (ε₀)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesOrdinal
Context triple: [Gentzen’s consistency proof for arithmetic, usesOrdinal, epsilon_0 (ε₀)]
  • A. usedOrdinal chosen
    Indicates that one entity is used as an ordinal indicator or position marker relative to another entity.
  • B. ordinalNumber
    Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
  • C. isRecursiveOrdinal
    Indicates that an ordinal has the property of being recursive, meaning its order structure can be fully described or generated by a computable (recursive) process.
  • D. orderOf
    Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
  • E. isLimitOrdinal
    Indicates that an ordinal is a limit ordinal, i.e., it is nonzero and has no immediate predecessor, being the limit of all smaller ordinals.
  • 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_69f22467626081908d5afea489590e96 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f6786c984c8190b7668a6232901b30 completed May 2, 2026, 10:19 p.m.
PD Predicate disambiguation batch_69f673c4abec8190bc2379e66f4af0a9 completed May 2, 2026, 9:59 p.m.
Created at: April 29, 2026, 6:31 p.m.