Triple
T2394147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riemann zeta function |
E47609
|
entity |
| Predicate | completedZetaDefinition |
P773
|
FINISHED |
| Object | ξ(s) = ½ s(s-1) π^{-s/2} Γ(s/2) ζ(s) |
—
|
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) = ½ s(s-1) π^{-s/2} Γ(s/2) ζ(s) | Statement: [Riemann zeta function, completedZetaDefinition, ξ(s) = ½ s(s-1) π^{-s/2} Γ(s/2) ζ(s)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedZetaDefinition
Context triple: [Riemann zeta function, completedZetaDefinition, ξ(s) = ½ s(s-1) π^{-s/2} Γ(s/2) ζ(s)]
-
A.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
defined
chosen
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
C.
domeCompleted
Indicates that the construction or formation of a dome structure has been fully finished.
-
D.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
E.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc87827d88190bb2351a688e6de32 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a3825c81909ec6111dfc165453 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.