Triple

T14314114
Position Surface form Disambiguated ID Type / Status
Subject Bernstein set E354908 entity
Predicate requiresAxiom P113929 FINISHED
Object axiom of choice for existence proof 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: axiom of choice for existence proof | Statement: [Bernstein set, requiresAxiom, axiom of choice for existence proof]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresAxiom
Context triple: [Bernstein set, requiresAxiom, axiom of choice for existence proof]
  • A. hasAxiom
    Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
  • B. axiom2
    Indicates that the relationship or action is taken as a fundamental, assumed truth within the system, serving as a base rule from which other statements are derived.
  • C. requiresBeliefIn
    Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
  • D. foundationAxiomHoldsIn
    Indicates that the foundation (or regularity) axiom is satisfied within a given model, structure, or context.
  • E. sufficientConditionFor
    Indicates that the truth or occurrence of one entity guarantees or ensures the truth or occurrence of another entity.
  • 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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de85b49e5481909b9ffab2d922e284 completed April 14, 2026, 6:21 p.m.
PD Predicate disambiguation batch_69de2a9515f4819081aabf251bca5878 completed April 14, 2026, 11:52 a.m.
PDg Predicate description generation batch_69de2e9ded24819099200349cf80e068 completed April 14, 2026, 12:10 p.m.
Created at: April 10, 2026, 1:12 a.m.