Triple

T14334586
Position Surface form Disambiguated ID Type / Status
Subject Ramanujan–Petersson conjecture E355436 entity
Predicate hasLocalForm P70766 FINISHED
Object bounds on Satake parameters 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: bounds on Satake parameters | Statement: [Ramanujan–Petersson conjecture, hasLocalForm, bounds on Satake parameters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLocalForm
Context triple: [Ramanujan–Petersson conjecture, hasLocalForm, bounds on Satake parameters]
  • A. hasLocalExpression chosen
    Indicates that something has a specific form, representation, or manifestation that is valid or defined only within a particular local context or region.
  • B. hasForm
    Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
  • C. hasComponentForm
    Indicates that one entity exists as a structural or compositional form or variant of another entity.
  • D. hasRealForm
    Indicates that an abstract, conceptual, or non-physical entity is associated with a concrete, physical manifestation or embodiment.
  • E. hasLocalCharacter
    Indicates that something possesses qualities, features, or significance that are specific to a particular locality or region.
  • 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_69d8278fa2108190bc0d0e7939c1eb03 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8c20d2148190bb534bef338e871d completed April 14, 2026, 6:49 p.m.
PD Predicate disambiguation batch_69de2a9515f4819081aabf251bca5878 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:13 a.m.