Triple

T8733465
Position Surface form Disambiguated ID Type / Status
Subject Hasse–Weil zeta function E207313 entity
Predicate localFactorAt P84546 FINISHED
Object finite prime of the base number field 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: finite prime of the base number field | Statement: [Hasse–Weil zeta function, localFactorAt, finite prime of the base number field]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: localFactorAt
Context triple: [Hasse–Weil zeta function, localFactorAt, finite prime of the base number field]
  • A. localStatus
    Indicates the current condition or state of an entity within a specific local context or environment.
  • B. localityCondition
    Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
  • C. locationScope
    Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
  • D. formsLocalityWith
    Indicates that two or more entities together constitute or define a specific locality or local area.
  • E. locationVariesWith
    Indicates that the location of one entity changes in dependence on, or as a function of, changes in 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_69ca8358e4008190898471a59b96c301 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d2a26988190acfda17f232e610a completed March 31, 2026, 11:47 p.m.
PD Predicate disambiguation batch_69cc457322b481908712a9630a17b954 completed March 31, 2026, 10:06 p.m.
PDg Predicate description generation batch_69cc572d99bc819097f36b140c2ee1ce completed March 31, 2026, 11:22 p.m.
Created at: March 30, 2026, 6:37 p.m.