Triple

T3780899
Position Surface form Disambiguated ID Type / Status
Subject Ulam sequence E85412 entity
Predicate hasUniquenessConstraint P38254 FINISHED
Object sum representation must be unique 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: sum representation must be unique | Statement: [Ulam sequence, hasUniquenessConstraint, sum representation must be unique]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUniquenessConstraint
Context triple: [Ulam sequence, hasUniquenessConstraint, sum representation must be unique]
  • A. uniquenessCondition chosen
    Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
  • B. hasUniqueStatus
    Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
  • C. isUniqueWithinSystem
    Indicates that an entity exists only once and has no duplicates within the defined system or scope.
  • D. isUniqueWithinStandard
    Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
  • E. isUniqueTo
    Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
  • 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_69aed937fa8881908208ef3801060826 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee634c6ac819099653c660c286746 completed March 9, 2026, 3:24 p.m.
PD Predicate disambiguation batch_69aee3d3c92c819081d9d5c45ef37a5d completed March 9, 2026, 3:14 p.m.
Created at: March 9, 2026, 3:12 p.m.