Triple

T27133868
Position Surface form Disambiguated ID Type / Status
Subject Pontryagin duality E681628 entity
Predicate codomainCategory P7031 FINISHED
Object opposite category of locally compact abelian groups 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: opposite category of locally compact abelian groups | Statement: [Pontryagin duality, codomainCategory, opposite category of locally compact abelian groups]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: codomainCategory
Context triple: [Pontryagin duality, codomainCategory, opposite category of locally compact abelian groups]
  • A. categoryCodomain
    Indicates that something belongs to, or is classified within, the codomain category of a given mapping or function.
  • B. codomain chosen
    Indicates the set of all possible output values that a function or mapping can produce, regardless of which values are actually attained.
  • C. canonicalCategory
    Indicates that an entity is assigned to its primary or standard category within a classification system.
  • D. categorifiedBy
    Indicates that something is assigned to or placed within a specific category by another entity.
  • E. functionCategory
    Indicates that one function is classified as belonging to a particular functional category or type.
  • 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_69eefacbcc2081909ebf00daa23f1981 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f62478fd0c81909b7de1d72aa0e2c0 completed May 2, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69f61b40f02081909bd9c3ea73249163 completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 9:06 a.m.