Triple
T19050645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirichlet eta function |
E466247
|
entity |
| Predicate | definitionDomain |
P4464
|
FINISHED |
| Object | Re(s) > 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(s) > 0 | Statement: [Dirichlet eta function, definitionDomain, Re(s) > 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definitionDomain Context triple: [Dirichlet eta function, definitionDomain, Re(s) > 0]
-
A.
notationDomain
Indicates a relationship where a notation system is associated with, or defined over, a particular domain in which it is valid or applicable.
-
B.
domainOfInterpretation
Indicates that the specified set constitutes the universe of discourse over which all variables and quantifiers in a logical system are interpreted.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
E.
definedOn
chosen
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc02597c8190b39fd2c7b7e42258 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.