Triple
T37475744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz zeta function |
E931273
|
entity |
| Predicate | hasSimplePoleAt |
P97140
|
FINISHED |
| Object | s = 1 |
—
|
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: s = 1 | Statement: [Hurwitz zeta function, hasSimplePoleAt, s = 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimplePoleAt Context triple: [Hurwitz zeta function, hasSimplePoleAt, s = 1]
-
A.
orderOfPoleAt
Indicates the location or index at which a function has a pole of a specified order.
-
B.
hasOrderOfPoleAtLatticePoints
Indicates that a function has poles of specified orders at each point of a given lattice in its domain.
-
C.
hasIsolatedSingularity
Indicates that a function has a singular point at which it is not analytic, but is analytic in some punctured neighborhood around that point.
-
D.
residueAt
Indicates the specific residue or position within a larger sequence or structure at which something is located, occurs, or is defined.
-
E.
hasPoleAt
chosen
Indicates that one entity possesses, contains, or is associated with a pole located at a specific point or position.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 3, 2026, 4:17 p.m.