Triple
T37475739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz zeta function |
E931273
|
entity |
| Predicate | definingConditionOnParameter |
P79479
|
FINISHED |
| Object | Re(a) > 0 |
—
|
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: Re(a) > 0 | Statement: [Hurwitz zeta function, definingConditionOnParameter, Re(a) > 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definingConditionOnParameter Context triple: [Hurwitz zeta function, definingConditionOnParameter, Re(a) > 0]
-
A.
definesConditionsFor
Indicates that one entity specifies or establishes the rules, requirements, or circumstances under which another entity is valid, applicable, or operates.
-
B.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
variableCondition
chosen
Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
-
D.
modificationCondition
Indicates the specific circumstances or requirements under which a change or modification to something is permitted, triggered, or becomes applicable.
-
E.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
- 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_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:17 p.m.